Skip to content
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

Implement basic network error handling #118

Merged
merged 3 commits into from
Apr 16, 2016
Merged

Conversation

stubailo
Copy link
Contributor

@stubailo stubailo commented Apr 16, 2016

Extracted from @martijnwalraven's PR #97

Fixes #78

@stubailo stubailo changed the title Add QueryObserver with callback for error responses Implement basic network error handling Apr 16, 2016
@stubailo stubailo added this to the alpha milestone Apr 16, 2016
@jbaxleyiii
Copy link
Contributor

@stubailo so this removes the handle.onResult yes?

@stubailo
Copy link
Contributor Author

Currently, it shims onResult to work: https://github.com/apollostack/apollo-client/pull/118/files#diff-748b449db1e130c8d777fa1ffa1e0725R293

But it might be kind of pointless to have that, since subscribe isn't much harder to call. Do you think it's OK to remove it?

@martijnwalraven
Copy link
Contributor

@stubailo: Yeah, the shim was just to not to have to change the tests while I was working on it. Definitely should be removed.

@stubailo
Copy link
Contributor Author

OK, going to do that now!

@stubailo
Copy link
Contributor Author

Filed a docs issue: https://github.com/apollostack/docs/issues/12

@stubailo
Copy link
Contributor Author

OK, looks like error handling works, we can implement the observable API on top of this.

@stubailo stubailo merged commit 42118fe into master Apr 16, 2016
@stubailo stubailo deleted the error-handling-minimal branch April 19, 2016 02:12
jbaxleyiii pushed a commit that referenced this pull request Oct 17, 2017
* Recommended that gql literals be imported in all files.

* Fixed error and switched to new graphql-tag package
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants