We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add an option to allow fetches to throw on an error rather than resolving with an error object
The text was updated successfully, but these errors were encountered:
Good idea - could also achieve this with custom fetcher.
Sorry, something went wrong.
@meabed I tried doing it in a custom fetcher, but GQLTS catches the error and resolves the promise with the error in the errors field.
errors
No branches or pull requests
Add an option to allow fetches to throw on an error rather than resolving with an error object
The text was updated successfully, but these errors were encountered: