You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great library, helps make things simple and clean!
A lot of changes and a more structured way of doing things looks to be right around the corner with Ember 2.0. As I'm working on making my app 'future proof' ( https://gist.github.com/samselikoff/1d7300ce59d216fdaf97 ), I want to make sure that this library doesn't violate the "data down, actions up" principle in particular. @asaf, could you share whether this library will be on board with the coming changes in Ember 2.0 and continue to be well supported as this changes? It looks like the Ember team plans to keep things mostly backwards compatible, but I would hope this project continues to evolve with Ember. For reference, there is some good discussion of the changes at emberjs/rfcs#15 and https://speakerdeck.com/tomdale/ember-2-dot-0-in-practice
Thanks
The text was updated successfully, but these errors were encountered:
@leejt489 sorry for the long delay I was in a holiday,
Sure, I am interesting in supporting Ember 2 but will continue to support 1.x for the time being,
We can create another branch in the near future to support 2 in parallel if the changes cannot live together for both versions.
@leejt489 I barely able to release versions that supports 0.x! now I push 1.x version,
I'm keeping this open but we'll have to look more closely when Ember 2 will come into a final shape.
Hi,
Great library, helps make things simple and clean!
A lot of changes and a more structured way of doing things looks to be right around the corner with Ember 2.0. As I'm working on making my app 'future proof' ( https://gist.github.com/samselikoff/1d7300ce59d216fdaf97 ), I want to make sure that this library doesn't violate the "data down, actions up" principle in particular. @asaf, could you share whether this library will be on board with the coming changes in Ember 2.0 and continue to be well supported as this changes? It looks like the Ember team plans to keep things mostly backwards compatible, but I would hope this project continues to evolve with Ember. For reference, there is some good discussion of the changes at emberjs/rfcs#15 and https://speakerdeck.com/tomdale/ember-2-dot-0-in-practice
Thanks
The text was updated successfully, but these errors were encountered: