-
Notifications
You must be signed in to change notification settings - Fork 202
Unit tests for issue #149 #153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unit tests for issue #149 #153
Conversation
@SethDavenport @danielfigueiredo related to an issue a user raised - any idea? made some tests to reproduce the issue. Initially I thought it might have been something related to the angular lifecycle hooks, but was able to reproduce it outside of angular. |
this._store.subscribe(() => this._store$.next(this._store.getState())); | ||
let x = store as any; | ||
|
||
this._store$ = Observable.from(x); //new BehaviorSubject(store.getState()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SethDavenport was looking at the interop unit tests from redux
this seems to fix the issue, although still bugging me to what the problem was with the BehaviorSubject
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weird - I wonder if there's a subtle difference in 'zoning' between the two ways of creating observables.
69a2d60
to
9b49d6e
Compare
* fix angular-redux#149 - chained actions should not get stale state, changed to create an observable from redux since redux 3.4x supports an observable shim * fix angular-redux#138 - ability to use select decorators in service Changing to use redux's observable, had to change how we created the initial observable. Use switchMap to switch streams once the store observable becomes available
2c3f554
to
381228a
Compare
No description provided.