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
Server Version: v2.35.0
OSS
v2.34 and below supported "extensions": null v2.35 and up crashes with: parsing PersistedQueryRequest failed, expected Object, but encountered Null
"extensions": null
parsing PersistedQueryRequest failed, expected Object, but encountered Null
I want the same behaviour as v2.34 in v2.35 and up
{"query":"{ __schema { queryType { fields { name } } } }","variables":null,"operationName":null, "extensions":null}
"extensions":null
Removing "extensions":null
The text was updated successfully, but these errors were encountered:
This is the commit that broke compatibility with "extensions": null
203b85a
Sorry, something went wrong.
Hi @jflambert, thank you for reporting that. We're looking into this right now and will get back when we have a fix.
This fix is going to arrive in 2.36 due to release this week.
@marionschleifer @manasag you can close this now...
pranshi06
No branches or pull requests
Version Information
Server Version: v2.35.0
Environment
OSS
What is the current behaviour?
v2.34 and below supported
"extensions": null
v2.35 and up crashes with:
parsing PersistedQueryRequest failed, expected Object, but encountered Null
What is the expected behaviour?
I want the same behaviour as v2.34 in v2.35 and up
How to reproduce the issue?
{"query":"{ __schema { queryType { fields { name } } } }","variables":null,"operationName":null, "extensions":null}
parsing PersistedQueryRequest failed, expected Object, but encountered Null
"extensions":null
from the query.Screenshots or Screencast
Any possible solutions/workarounds you're aware of?
Removing
"extensions":null
The text was updated successfully, but these errors were encountered: