processing data option in beforeCreate hook makes it impossible to use this in data option about vue-rx HOT 6 CLOSED

released 2.0.0.

from vue-rx.

I'm not sure why RxJS has to be integrated in such a cloaked way by Vue (is there some benefit I'm not aware of)? RxJS is what it is, just another API, a utility that can be imported and used where it and it's wonderful operators might find a usage.

Integrating RxJS as a Vue Directive would be better. Then in the directives handler you can use RxJS to it's maximum benefit. I just saw the following awesome article where the Pointer-Events API was integrated into Vue via a Directive. The same integration could be done for RxJS.

https://benjaminlistwon.com/blog/strategies-for-extending-vue

The RxJS API should be just like Lodash or any other API, just an option one is free to use in component method, computed or watch functions.

from vue-rx.

@zoomclub RxJS may be used to handle either DOM events or back-end socket.io data push. If you are using Vue, I don't think RxJS is quite useful for DOM handling, since Vue (as a view tool) already has plenty of gadgets to interact with the DOM. But Vue doesn't provide any model or back-end data tools. That's where RxJS can help. I usually use this plugin to link socket.io data push from back-end and vue in the front-end.

from vue-rx.

@beeplin Still need a way to turn DOM events into a stream/observable in Vue component template. A directive would essentially just wrap the following RxJS operator:

http://reactivex.io/rxjs/class/es6/Observable.js~Observable.html#static-method-fromEvent

<div v-rxjs:event-type=“handler”> would be nice, because RxJS offers something unique.

from vue-rx.

I think it might be better if we change the API to use a separate option instead:

data () {
  // normal state
  return { ... }
},
rx: {
  key: someObservable$
},

This more explicitly separates observables vs. normal state, and solves the issue you are running into.

from vue-rx.

@yyx990803 sure, that would be great. :)

from vue-rx.