You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Errors are not JSON Serializable, When schema.graphql file is generated using following command ./manage.py graphql_schema --schema myproject.schema.schema --out schema.graphql
The type generated for error is scalar ExpectedErrorType
In Other words, I can say that Field "errors" must not have a selection since type ExpectedErrorType has no subfields. .
This message can be received by graphiql (Provided by django) or Altair, when you will provide an invalid token and will try to write as follows.
{
"errors": [
{
"message": "Field \"errors\" of type \"ExpectedErrorType\" must not have a sub selection.",
"locations": [
{
"line": 18,
"column": 11
}
]
}
]
}
Prerequisites
For more information, see the CONTRIBUTING guide.
Description
Errors are not JSON Serializable, When schema.graphql file is generated using following command
./manage.py graphql_schema --schema myproject.schema.schema --out schema.graphql
This command I got from the documentation of Graphene-python
https://docs.graphene-python.org/projects/django/en/latest/introspection/
The type generated for error is
scalar ExpectedErrorType
In Other words, I can say that
Field "errors" must not have a selection since type ExpectedErrorType has no subfields.
.This message can be received by graphiql (Provided by django) or Altair, when you will provide an invalid token and will try to write as follows.
Steps to Reproduce
Just implement it according to the documentation and do as I stated above.
Expected behavior
Actual behavior
The expected behavior are producing with
But on the front-end side Accessibility as follows is required to read the error message.
Requirements
No additional requirements except mentioned in the documents.
The text was updated successfully, but these errors were encountered: