Closed heartsentwined closed 10 years ago
Thanks for posting this! Definitely need more docs.
I think with 0.1.4 you should be able to get away with not having the initializer. Ember's default resolver will automatically check the namespace.
I thought the implementation of transformFor
means that I have to register the transform beforehand?
You only have to register it if you break conventions. By default container.lookup('transform:raw')
will resolve to Namespace.RawTransform
.
Ah actually as I type this, I see that you added it to the Ep
namespace rather than your app's namespace. In that case you would have to register it.
Oh thanks for the clarification! I'm still wrapping my head over the DI stuff at ember
As an fyi, I have refactored the serialization layer and there is no longer a difference between serializers
and transforms
. The only practical application here is that the transform should be renamed to RawSerializer
. Moreover, since transforms and serializers are now one and the same, you can actually have attributes with model types (e.g. Ep.attr 'post'
) but I digres....
Another "issue" as a reference for future googlers. If there's a docs site or something like that, I'd be glad to contribute over there :smile:
In
0.1.3
:0.1.4
: