Skip to content

Fix errors raising TransportProtocolError with the graphql-ws protocol #299

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

Merged
merged 2 commits into from
Feb 22, 2022

Conversation

leszekhanusz
Copy link
Collaborator

Should fix issue #294

@codecov-commenter
Copy link

codecov-commenter commented Feb 21, 2022

Codecov Report

Merging #299 (eafb44a) into master (0084b95) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##            master      #299   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           26        26           
  Lines         2068      2070    +2     
=========================================
+ Hits          2068      2070    +2     
Impacted Files Coverage Δ
gql/transport/websockets.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0084b95...eafb44a. Read the comment docs.

@leszekhanusz leszekhanusz merged commit d3be916 into graphql-python:master Feb 22, 2022
@leszekhanusz leszekhanusz deleted the fix_graphqlws_errors branch March 12, 2022 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

graphql-ws 'error' packet's .payload field should be array, not object
2 participants