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
If you pass an explicitly-set 0 value through the graphQL layer, it gets silently dropped because 0 is falsy in JS and the checks in the graphQL layer aren't very specific. I have a nullable integer field where 0 and null mean two different things, but when I send a 0, it gets converted to null.
If you pass an explicitly-set
0
value through the graphQL layer, it gets silently dropped because0
is falsy in JS and the checks in the graphQL layer aren't very specific. I have a nullable integer field where0
andnull
mean two different things, but when I send a0
, it gets converted to null.You can see the issue in this method: https://github.com/jagql/framework/blob/master/lib/graphQl/resolvers.js#L66
The text was updated successfully, but these errors were encountered: