We are excited to announce the release of Ember Data 2.0, the second stable release since 1.13 that includes significant improvements, cleanup, and cruft removal. As previously discussed, Ember Data releases occur in lockstep with Ember, to help developers better reason about compatibility between these libraries. Ember Data 2.0 is designed to be used in tandem with Ember 2.0, and like Ember 2.0,
Release 2.0.0 (August 20, 2015) Breaking Changes Usaved deleted records are no longer removed from hasMany relationships and RecordArrays returned by the store In Ember Data 1.13 once a record was marked as deleted it was removed from all of the RecordArrays and hasMany arrays it belongTo. This made it difficult to create UIs where a user could flag a record for deletion but still allow the user t
TL;DR Ember Data 1.0 is coming soon. We have a few last features to land before we can confidently make guarantees around not breaking the API. Specifically: A guarantee that if one side of a two-way relationship changes, the other side will remain in sync, even if it hasn't loaded yet. All relationships will become async, but DataBoundPromises will make them work well in observers, computed prope
by Vic Ramon on September 15, 2013 Update: June 26, 2014 This tutorial is now out of date, and you should instead look at Vic Ramon's Ember Tutorial for a tutorial introducing Ember with Rails. Update: November 8th, 2013 Some of the instructions below are out of date, particularly the code in the store.js file. Please look at the Ember Data Rails Example that I have posted to Github for correct, u
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く