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
Stitched queries that use @include or @skip directives that refer to a variable return a message that the variable is not declared. This effectively means that @include and @Skip don't work when stitching as the primary use-case would be having them handle a variable.
To Reproduce
Steps to reproduce the behavior:
Create a stitched schema
Attempt to use an @include directive with a boolean field in playground. For example:
Note the error: "The following variables were not declared: YOUR_VARIABLE."
Expected behavior
Same behavior as if the literal true or false were passed to the @include directive.
Additional context
In some limited debugging, it looks like these variables are not in the _usedVariables list in AllVariablesUsedVisitor.cs, I'm guessing they're not being sent to the client endpoint, but I haven't dug-in that deep.
The text was updated successfully, but these errors were encountered:
OK, this one is more complicated :) the query rewriter does not correctly visit the directive hence the variables are not touched. I will look at this tomorrow.
Describe the bug
Stitched queries that use
@include
or@skip
directives that refer to a variable return a message that the variable is not declared. This effectively means that @include and @Skip don't work when stitching as the primary use-case would be having them handle a variable.To Reproduce
Steps to reproduce the behavior:
@include
directive with a boolean field in playground. For example:"The following variables were not declared: YOUR_VARIABLE."
Expected behavior
Same behavior as if the literal
true
orfalse
were passed to the@include
directive.Additional context
In some limited debugging, it looks like these variables are not in the
_usedVariables
list inAllVariablesUsedVisitor.cs
, I'm guessing they're not being sent to the client endpoint, but I haven't dug-in that deep.The text was updated successfully, but these errors were encountered: