GraphQL schemas being nullable by default is a major pain point of GraphQL for client developers today because it's impossible to tell a field nullable for product reasons vs a field nullable for error reasons (more details in Benjie's excellent post there: https://benjie.dev/graphql/nullability/)
It would be nice to support onError in Ariadne and allow the clients to opt-out of null bubbling when they can handle errors by looking at the errors array.
Happy to help anyhow I can or answer any question.
GraphQL schemas being nullable by default is a major pain point of GraphQL for client developers today because it's impossible to tell a field nullable for product reasons vs a field nullable for error reasons (more details in Benjie's excellent post there: https://benjie.dev/graphql/nullability/)
It would be nice to support
onErrorin Ariadne and allow the clients to opt-out of null bubbling when they can handle errors by looking at theerrorsarray.onErrorapollographql/apollo-kotlin#6860Happy to help anyhow I can or answer any question.