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
Describe the bug
The schema can include default values for query arguments. The doc-viewer shows this value next to the query argument name. In the case of false and null this does not happen. In the introspection query, default values are always sent as a string:
not set ->"defaultValue": null
null -> "defaultValue": "null"
false -> "defaultValue": "false"
I think this is the current code that is used to parse the incoming value:
Thanks for reporting this! I'd look into it as soon as I can. Note if you identify the issue, you can always create a PR. That way it can be resolved faster, otherwise I'll try to take a look when I can
Describe the bug
The schema can include default values for query arguments. The doc-viewer shows this value next to the query argument name. In the case of
false
andnull
this does not happen. In the introspection query, default values are always sent as a string:"defaultValue": null
null
->"defaultValue": "null"
false
->"defaultValue": "false"
I think this is the current code that is used to parse the incoming value:
altair/packages/altair-app/src/app/modules/altair/services/gql/oldBuildClientSchema.ts
Lines 334 to 336 in 18ab729
To Reproduce
Steps to reproduce the behavior:
null
orfalse
null
orfalse
Expected behavior
The doc-viewer shows the default value as
null
orfalse
Screenshots
true
:false
:null
:Desktop:
The text was updated successfully, but these errors were encountered: