heartsentwined
heartsentwined
Current workaround is to pass just about any "dummy" statement in the catch block: ``` coffeescript try foo catch e '' # do nothing baz ``` ``` coffeescript try foo...
@michaelficarra same happens to other structures too, e.g. ``` coffeescript if condition # TODO - to be implemented else return false ``` would throw an error at the `# TODO`...
Thanks for the pointer, I'll join discussions over there.
I like the idea, although forgive me for nitpicking issues. I think that this concern should belong to `Ember.Auth.Strategy` itself. Would you mind moving this upwards to the master `serialize()`...
What is the `ember-model` version?
Blame `ember-model` either for changing the find-by-id api or for being buggy then :)
huh? Has something changed in the adapters too?
The integration model itself is pretty minimal, first it [patches](https://github.com/heartsentwined/ember-auth-module-ember-model/blob/master/lib/module/ember-model.em#L35) the `Ember.RESTAdapter`: ``` coffeescript Ember.RESTAdapter.reopen _ajax: (url, params, method, settings) -> super url, params, method, self.auth._strategy.serialize(settings || {}) ``` Then...
Got it. It is a priority problem. `ember-model`, unlike the other two persistence libs, requires you to declare an _instance_ of the adapter alongside model declarations. ``` javascript App.User =...
Indeed the same happened with `ember-auth` itself, pre `9.x`. It required you to `create()` an auth instance immediately when you write the config, so the ordering was critical (right after...