Jason Dobry

Playing around with this idea here: https://github.com/js-data/js-data/tree/swappable-store Most of the tests pass even when using ImmutableJS as the internal in-memory store. Need to figure out what to do about js-data's...

Yeah, something like this might work

v3 is much more flexible, with functionality split into various components. This makes it much easier to create say, an `ImmutableStore` class as an alternative to v3's `DataStore` class, which...

I'm changing this issue's scope to: Create a `js-data-immutable` project which would essentially be: ``` js import {Container} from 'js-data' import Immutable from 'immutable' export default Container.extend({ constructor: function ImmutableStore...

@AlexandreBonaventure That's really cool! I was just talking with @yyx990803 about creating something like this a couple weeks ago at UtahJS Conf!

@tribou I can't give a definitive answer just yet. I would need to familiarize myself with ImmutableJS and actually take a crack at implementing js-data-immutable before I knew. p.s. We...

Can you try something like this and see how it works for you before I think about adding more options to js-data? The goal of the architecture changes from v2...

I'll document the examples you and I posted and use that as the recommended approach for now, and will see what people say down the line.

``` javascript JSData.DS.prototype.softDestroy = function (resourceName, id, options) { var _this = this; var softDeletedItem; return this.destroy(resourceName, id, { beforeDestroy: function (Resource, attrs) { return Resource.update(id, { deleted_at: new Date()...

v2 ``` javascript JSData.DS.prototype.softDestroy = function (resourceName, id, options) { return Resource.update(id, { deleted_at: new Date() }); }; ```