-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Make it possible to use an existing observable implementation #149
Comments
`refetch()`, `stopPolling()`, `startPolling()` are part of `queryObservable` not `subscription`
updated webpack.md with info on #import syntax for fragments
Could you guys please document your issues and pull requests with an actual description that describes what is wanted and/or what is being merged? I would prefer not to have to hunt through the code-base and the diffs just to understand the jest of a PR. E.g. this one — it references #196, but neither actually says what it's about. I'm interested in this, since I consider redux a great pattern for applications, I've worked extensively with redux-observables and rxjs and: reading the source code of this repository gave me a real scare — how is this code-base maintainable? As such, I'd like to understand what is going into the library — especially when it comes to clearly thought through concepts like observables (as opposed to less well thought through pieces of code, like the |
For example, to easily integrate with RxJS.
The text was updated successfully, but these errors were encountered: