Robert Porter

Results 11 comments of Robert Porter

Looking at [the signature of `beforeDestroy()` where it's called](https://github.com/js-data/js-data/blob/cacc5e5be01f1493a5f9cce499776d7b6e817700/src/datastore/async_methods/destroy.js), it seems it would be something more like: ``` javascript beforeDestroy: function(Resource, attrs) { var id = attrs[Resource.idAttribute]; attrs.deleted_at = new...

At the moment, the best way to get this functionality in an project is to override `DS.destroy()`: ``` javascript let DSDestroy = DS.destroy; DS.destroy = function(resourceName, id, options) { let...

Woah, it's a double bluff. Destroying, but not really, resulting in an error that's actually the result. I know a PHP dev who would suicide if he had to understand...

Until it's implemented in JSData, I'll probably use something like: ``` javascript var Important = DS.defineResource({ beforeDestroy: DS.utils.Promise.reject }); JSData.DS.prototype.softDestroy = function(resourceName, id, options) { return DS.update(resourceName, id, { deleted_at:...

This is something I was postponing until the library had some critical feedback. Are you using the library currently, or thinking of using it?

> @robertdp Any chance here? I'm currently trying to decrease the size of my manual additions in my package set 😁 @i-am-the-slime Let me update the project to 0.15 and...

"Better late than never" -- https://github.com/purescript/package-sets/pull/1198

The Rx* libraries solve this with the `share` operator. http://reactivex.io/rxjs/class/es6/Observable.js~Observable.html#instance-method-share A naive approximation of this is: ```purescript share :: forall a. Event a -> Effect (Event a) share source =...

It's definitely a common use case. Would a definition like ```purescript share :: forall a. Event a -> Effect { event :: Event a, unsubscribe :: Effect Unit } share...

`merge` is what most "reactive" JS libraries call the function, and it's basically an effectful `append`/`fold` so it made sense. `oneOf` implies something alternative-based doesn't it? I started considering wrapping...