Repository navigation
Nested Input type object need a direct usage to be registered correctly #266
Description
with version 5.5.1
this doesn't work ( error during graphql service registration )
input A {
v :Int
}
input B {
a : A
}
type Query {
q1 (b: B ) : Int
}seems that A is not usabe as nested input object if hasn't been called directly by some method in the graphql interface
this WORKS instead.. ( the dumb ) method seems to be required to register A as input type which is required by B... seems a bug in the library to me.. , the previously schema didn't worked neither with A as normal type
input A {
v :Int
}
input B {
a : A
}
type Query {
q1 (b: B ) : Int
dumb(a:A):Int
}
Activity
vojtapol commentedon Feb 4, 2020
Related to #261
shahmalhar commentedon Mar 24, 2020
This is a major bug, is anyone looking into this or is there an ETA?
oryan-block commentedon Oct 3, 2026
Closing as a duplicate of #479. Nested inputs are discovered from your input class properties (see
NestedInputTypesTest), so this works on 14.x when the class exposes a matching public getter or field. The failure that remains is when there is no matching property (typo, private field, getter casing) or the resolver takes aMap. That is #479, and the misleading error message is #422. Workaround: register the nested input in the dictionary.