Multiple queries / mutations in single request stop at first error about lighthouse HOT 3 CLOSED

Lighthouse works as expected here, I added a test just to be sure: 2ecc00c.

Consider https://spec.graphql.org/draft/#sec-Handling-Field-Errors. GraphQL repsonses will always conform to what is promised in the schema. If a non-nullable field at any level of the query tree has an error, that entire level is invalidated and the error bubbles up to the next level. If you you already on the top level, you will get no data at all.

from lighthouse.

Hey @spawnia, thanks for the clarification, I wasn't aware of that distinction, pretty new to GraphQL.

Quick question, changing the return types to nullable did indeed work on mutations but not for my queries example, is there a reason for that, other than nullable return types ?

from lighthouse.

Sorry for commenting in a closed issue.

Using lighthouse v6, I would like to opt to make my mutations to stop if one of them fails. Is it possible to achieve such thing?

For example, this is an pseudo request a client is making:

mutation update_and_insert {
   updateRow {...}
   insertRow {...}
}

Both of these mutations are decorated with @field (resolver: "path/to/mutation@method")
The updateRow is prone to throw exceptions due to many factors. When it happen, I would like to prevent insertRow to insert new row in database.
Does anybody knows if it's possible to run both of mutations inside a "transaction block" without creating a third mutation just to wrap updateRow and insertRow?

from lighthouse.