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
Question.
The Graphql Spec seems to have support for replacing required value with the default value. I think it was supported in version 2 as well, but currently if I try to generate by replacing query Media($includeAny:Boolean!) with query Media($includeAny:Boolean = true) it gives error Variable includeAny of type Boolean used in position expecting type Boolean!. Is this feature implemented or am I missing something? If it's missing is it possible to implement it?
The text was updated successfully, but these errors were encountered:
Hi! Could it be that the field you're using the variable with expect a Boolean!? If yes, it should just be a matter of declaring your query like this: query Media($includeAny: Boolean! = true)
If I try to use it like that then the server gives Variable \"$includeAny\" of type \"Boolean!\" is required and will not use the default value. Perhaps you meant to use type \"Boolean\".. Its a third party server and I have no control over it, so I was wondering if it is standard(according to specs) to implement it like that in server side. I have like little to no idea about graphql-servers validation like it is according to specs or anything else. If its nothing like that then the issue could be closed or there could be support for query without ! sign for default values.
Message sent to sever is like query Media($includeAny!:Boolean = true)
Question.
The Graphql Spec seems to have support for replacing required value with the default value. I think it was supported in version 2 as well, but currently if I try to generate by replacing
query Media($includeAny:Boolean!)
withquery Media($includeAny:Boolean = true)
it gives errorVariable includeAny of type Boolean used in position expecting type Boolean!
. Is this feature implemented or am I missing something? If it's missing is it possible to implement it?The text was updated successfully, but these errors were encountered: