Help needed debugging NonNullableValueCoercedAsNullException #2760
-
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
Did you solve your issue yet? |
Beta Was this translation helpful? Give feedback.
-
|
No, not yet. |
Beta Was this translation helpful? Give feedback.
-
|
Let me give you some generalised information about
However looking at this stack trace I can see its no field execution but rather the (The I am a little puzzled here because this is "input arguments" and not output field values. I need to sit down and spend some time on this to find a cause. (also as an aside I think we have an opportunity to make this "field argument value" work lazy. |
Beta Was this translation helpful? Give feedback.
-
|
I have created an issue fior this. I will discuss it more on the issue. |
Beta Was this translation helpful? Give feedback.
-
|
See my comment there about possible custom scalars breaking contract |
Beta Was this translation helpful? Give feedback.
-
|
This turned out to be my own fault, because the variables was actually { |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Let me give you some generalised information about
NonNullableValueCoercedAsNullExceptionand then I will look further.NonNullableValueCoercedAsNullExceptionis thrown when a field that declares itself to be non nullable in fact at runtime does return a null value (sayname : String!which then returns a null name value say)However looking at this stack trace I can see its no field execution but rather the
MaxQueryDepthInstrumentationtraversing a input query and trying to get certain values.(The
Field '' has coerced Nullis a bug - we should fix that useless error message)I am a little puzzled here because this is "input arguments" and not output field values.
I need to sit down and…