David Luecke
David Luecke
Disregard my delete comment :laughing: exactly what you said should work.
It probably will work if you set the [`lean` option to `true`](https://github.com/feathersjs-ecosystem/feathers-mongoose#serviceoptions). You can also probably get the same functionality by using an `after` `remove` [Feathers service hook](https://docs.feathersjs.com/api/hooks.html).
It looks like the tests are passing, so is #190 still an issue?
That's great. Though I don't think the original Redis driver would still work with this change. I'm thinking it'd either should be its own adapter or feature detect the driver....
Can you put this into a pull request?
I really like the idea but I'm wondering if `feathers-sync` is the right place for it. This module is intended for running multiple instance (e.g. Heroku dynos) of the same...
`feathers-sync` publishes the [service events](https://docs.feathersjs.com/api/events.html#service-events) to all servers. It doesn't really trigger the service call itself. Publishing the events is done by hooking into the service event emitter and replacing...
How does the reactive model look like? Definitely not opposed to adding this as a feature but I currently can't think of a good way to make that possible. Basically...
So what I think would need to happen is add unique server name to the `sync-out` event (in https://github.com/feathersjs-ecosystem/feathers-sync/blob/master/lib/core.js#L47): ```js return app.emit('sync-out', { event, path, data, context, name: someServerName });...
Sounds great, let me know if you need anything!