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
When we typing directive argument as an Input and then invoke this directive with argument correct struct value of passed argument of directive invocation is actualy empty object.
Steps To Reproduce:
Compile this:
directive @some(value:Bar) on OBJECTinput Bar{
one:String!
two:String}type Foo @some(value:{one:"Hey!"}){
any:String!}
greabock
changed the title
Directive invocation argument value is empty when it's an Object
Directive invocation argument value is empty when it's an Input
Jan 14, 2018
The problem is that the selection of types from the "future" stack (this is stack of invocable types) was not recursive (that is, if type A adds a type B to the stack during the build of dependencies - it does not build). In this connection, the meaning of the input (which is the Invocation) inside the directive (which is also an Invocation) is not compiled.
In addition, the dependency graph between call and type definition during the resolves of this type was incorrectly built.
Description:
When we typing directive argument as an
Input
and then invoke this directive with argument correct struct value of passed argument of directive invocation is actualy empty object.Steps To Reproduce:
Compile this:
then
Expected result:
Instance of
InputInvocationBuilder
filled with actual value ({one: "Hey!"}
).What happens instead?
Empty Instance of
InputInvocationBuilder
:The text was updated successfully, but these errors were encountered: