Use TC39 proposal for Symbol.observable to turn resources into Observables

See this (+ polyfill).

The idea is that instead of monkey patching resources into Observables, we should just implement Symbol.observable on them and create an observable by passing them into Observable.from.

For example,

import {Observable} from 'rxjs';
import app from './app'; // some feathers app

const messages = app.service('messages');

const messages$ = Observable.from(messages.find()); // messages.find() has a Symbol.observable member

messages$
  .switchMap(/* whatever */)
  // etc. ...

This removes the direct dependency on RxJS and moves toward the proposed standard. See the implementation in redux.

[daffl]

Thank you! This would probably also solve #41. Would be nice to implement it with the next release but I might not get to look into this until after.

[daffl]

After a little more research (inhttps://github.com/feathersjs-ecosystem/feathers-reactive/tree/symbol-observable-latest), I think we can close this. @j2L4e’s implementation of a .watch method was the way to go here.