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
It seems we don't need to use await anymore with the subscribe method since the latest 3.3.0a3 pre-release.
await
subscribe
This causes current gql tests to fail with either:
TypeError: object async_generator can't be used in 'await' expression
TypeError: object ExecutionResult can't be used in 'await' expression
That new interface seems cleaner but could you please maybe indicate that breaking change in the release notes?
Thanks,
The text was updated successfully, but these errors were encountered:
Right, this is a breanking change that is now mentioned in the release notes. It mirrors a similar change in GraphQL.js.
Sorry, something went wrong.
No branches or pull requests
It seems we don't need to use
await
anymore with thesubscribe
method since the latest 3.3.0a3 pre-release.This causes current gql tests to fail with either:
TypeError: object async_generator can't be used in 'await' expression
TypeError: object ExecutionResult can't be used in 'await' expression
That new interface seems cleaner but could you please maybe indicate that breaking change in the release notes?
Thanks,
The text was updated successfully, but these errors were encountered: