These are chat archives for orbitjs/orbit.js
I think the key simplifications we're discussing are that:
1) unordered sets should be simple POJOs so that patch operations work upon them
2) ordered sets can be arrays, which patch operations also work upon
3) sets that maintain record identity can be simple POJOs keyed by
source.query()(which only return a single value) and to use observables for
source.liveQuery()(which returns a stream of updates).
queryRecordsproposal - it seems natural to keep that in the EO.Store and simply lookup the results in the identity map before returning them
addondirectory achieve the same thing?
WRT to loading ES6 modules directly, I think we want to add both the ember-orbit and orbit.js source trees into the ember app’s broccoli pipeline