Raphael

Ah, slightly messed up my codesandbox sorry... https://codesandbox.io/p/devbox/optimistic-noyce-kdrtx4?file=%2Fdocument.graphql so now with ``` query user { ... on Query @defer { user(id: 1) { id username email } } } ```...

What you are suggesting would be flagged by a linter as a "useless conditional" and rely on developer to remember that its defered and to add the check From a...

I rereviewed the example i sent, and indeed it does the right thing... I now copied my example from the first post, and i can repro.... the real crux of...

Please refer to https://github.com/apollographql/apollo-client/issues/12817#issuecomment-3139743770 Its not defered, but one of its child field is, and is non-nullable, when this field returns an error, the server will patch `resolve2` with a...

You can have both data & error, thats perfectly valid GQL response coming out of useQuery, in my case i have (partial) data & error

So, we are using apollo with `errorPolicy: "all"`, so thats NOT using an error handling client, as far as i understand. Did not know semanticNonNull existed, great find, but thats...

Sorry i missed your reply, semanticNonNull is a server config, defer is a client opt-in, if the client decides to defer a field, that config cannot be in the server...

And i will also emphasize again, your repeated proposal of using `semanticNonNull` (which is a SERVER-side annotation) is incompatible without our desire of using defer which is a CLIENT-side annotation,...

> Error always bubble to the nearest nullable parent (starting with the field), regardless if defer is used or not. Errors bubble to the nearest NULLABLE parent in non-defer Errors...

Okay let me ask you a different question: Is 4 month of discussion going round in circle really worth it vs just catering our need motivated by observed behavior from...