Creating "invalid" records in memory / triggering persistence about orbit HOT 4 CLOSED

ember-data, for example, uses 'save' to persist data, but as far as I can tell orbit does not have a specific persist command.

from orbit.

Orbit takes a different approach from ember-data. In ember-data, records maintain state themselves. In orbit, the state of records exists exclusively in sources. In other words, orbit doesn't maintain temporary editing state in record objects which then need to be "saved".

I am working on a pattern in ember-orbit to create temporary sources that act as "editing contexts". The idea is that data is copied to a context, edited in isolation, and the operations are then squashed and applied back to the main source in a single transaction (or the context and its changes can be discarded). I think this is a more robust and clean approach to saving records transactionally. I'll be illustrating this pattern in the example project I've mentioned.

from orbit.

Makes sense, looking forward to seeing the pattern in the example project!

from orbit.

The concept of "editing contexts" has materialized as store forking and merging, as documented here: http://orbitjs.com/v0.15/guide/data-stores.html#Forking-stores

Also, there's an ember-orbit example project that illustrates the concept: https://github.com/cerebris/peeps-ember-orbit

from orbit.