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
Is your feature request related to a problem? Please describe.
When making introspection requests trough graphql-protect, and including for example the isDeprecated field on __InputValue, or the includeDeprecated argument on an args field, graphql-protect will throw an error. This is an example of an introspection response of graphql-protect in front of an apollo router API:
{
"data": null,
"errors": [
{
"message": "Cannot query field \"isDeprecated\" on type \"__InputValue\".",
"locations": [
{
"line": 64,
"column": 3
}
]
},
{
"message": "Cannot query field \"deprecationReason\" on type \"__InputValue\".",
"locations": [
{
"line": 65,
"column": 3
}
]
},
{
"message": "Unknown argument \"includeDeprecated\" on field \"__Field.args\".",
"locations": [
{
"line": 32,
"column": 5
}
]
},
{
"message": "Unknown argument \"includeDeprecated\" on field \"__Type.inputFields\".",
"locations": [
{
"line": 41,
"column": 3
}
]
},
{
"message": "Unknown argument \"includeDeprecated\" on field \"__Directive.args\".",
"locations": [
{
"line": 19,
"column": 7
}
]
},
{
"message": "Cannot query field \"isDeprecated\" on type \"__InputValue\".",
"locations": [
{
"line": 64,
"column": 3
}
]
},
{
"message": "Cannot query field \"deprecationReason\" on type \"__InputValue\".",
"locations": [
{
"line": 65,
"column": 3
}
]
},
{
"message": "Unknown argument \"includeDeprecated\" on field \"__Field.args\".",
"locations": [
{
"line": 32,
"column": 5
}
]
},
{
"message": "Unknown argument \"includeDeprecated\" on field \"__Type.inputFields\".",
"locations": [
{
"line": 41,
"column": 3
}
]
},
{
"message": "Cannot query field \"isDeprecated\" on type \"__InputValue\".",
"locations": [
{
"line": 64,
"column": 3
}
]
},
{
"message": "Cannot query field \"deprecationReason\" on type \"__InputValue\".",
"locations": [
{
"line": 65,
"column": 3
}
]
}
]
}
Describe the solution you'd like
I deduced that this was caused due to missing support in the gqlparser library for these fields, as it was missing recent graphql spec compatibility. In a recent PR this has been fixed, and since 2.5.22 support for introspection of deprecated input values should be present.
So a simple update of the dependency should fix this. I would also like to see a note in the readme to educate users about the graphql spec compatibility.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When making introspection requests trough graphql-protect, and including for example the
isDeprecated
field on__InputValue
, or theincludeDeprecated
argument on anargs
field, graphql-protect will throw an error. This is an example of an introspection response of graphql-protect in front of an apollo router API:Describe the solution you'd like
I deduced that this was caused due to missing support in the
gqlparser
library for these fields, as it was missing recent graphql spec compatibility. In a recent PR this has been fixed, and since2.5.22
support for introspection of deprecated input values should be present.So a simple update of the dependency should fix this. I would also like to see a note in the readme to educate users about the graphql spec compatibility.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: