Problem
Currently, if the user wants to use RxJS or any other reactive library except light-observable, he needs to use from and its analogs in every epic. stapp-rxjs package solves this problem partially but is not convinient.
Solution
Libraries like redux-observable and recompose try to solve this problem by exposing a function (e.g.: setObservableConfig in recompose) that sets all needed transformations globally.
Todo:
- Create and expose a method to set transformations globally.
- Add a boolean field to module interface, that will, if set to
true, force stapp to ignore global config and provide that module the native observable.
- Add predefined config to
stapp-rxjs
Problem
Currently, if the user wants to use RxJS or any other reactive library except light-observable, he needs to use
fromand its analogs in every epic.stapp-rxjspackage solves this problem partially but is not convinient.Solution
Libraries like redux-observable and recompose try to solve this problem by exposing a function (e.g.:
setObservableConfigin recompose) that sets all needed transformations globally.Todo:
true, force stapp to ignore global config and provide that module the native observable.stapp-rxjs