How to store.createRecord().save() without immediately effecting the client side instance?

[v3ss0n]

Thanks a lot. But avoding createRecord/and every update functions , actually defeats the purpose of using Emberjs because ember-data is very powerful.

here is my current solution. i think there are much proper ways to do so.

Proper way to monitor state changes of the records?

I am using a service at the backend that push data to store in realtime, via EventSource . While store.createRecord().save() is pushing into backend , it conflicts with client side store , and it cause duplicated records. As suggested by ember community at slack , i check the state of isSaving at records array , to make sure it won’t conflict , and then push later when isSaving is false . So it pushes to client side store after data is saved properly. I use Ember.run.later with an interval to …