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
currently in graphql-java we can't distinguish between provided nulls and unprovided values,
even worse - the query just fails
see the official graphql pr here graphql/graphql-spec#83
Activity
andimarek commentedon May 13, 2017
comment by @bbakerman:
We could extend the grammar to allow a NullValue to be captured in syntax eg:
field (arg : null)
The trick then would be how best to tell DataFetchers that the value is null literal versus not present
ieugen commentedon May 13, 2017
@andimarek : java.util.Optional could do that, no ?
graphql-java#427 - NullValue support plus "provided null" versus "not…
bbakerman commentedon May 14, 2017
java.util.Optional would indeed do it
but we would have to change the current behaviour from
to
Optional argValue = environment.getArgument("arg")
This would break all existing code. Its a tricky one
ieugen commentedon May 15, 2017
As they say: If you wish to make an omelet... release version 4 :).
andimarek commentedon May 15, 2017
see #434
graphql-java#427 added null support but have not added optional argum…
graphql-java#427 added spec tests and values resolver support
graphql-java#427 more tests and a specific exception for coerced null…
graphql-java#427 added null support but have not added optional argum…
graphql-java#427 added spec tests and values resolver support
graphql-java#427 more tests and a specific exception for coerced null…
graphql-java#427 - more tests for null variables values
graphql-java#427 - extra test for This unordered map should not conta…
#427 TDD driven null support (#452)
bbakerman commentedon May 28, 2017
Implemented via PR #452
Merge remote-tracking branch 'upstream/master'