Add onError request parameter#4378
Conversation
Test ReportTest Results
Code Coverage (Java 25)
Changed Class Coverage (2 classes)
|
|
One possible approach might be to "maintain" the old directive WHILE adding the new ExecutionInput based approach. That way anyone who has used the old will be able to migrate to the new without breaking. This will cost time and complexity of course but it will be "less impactful" to current users That said - at what point is the kill date? One could argue it was "experimental" and hence the kill date is immediate as this PR has done |
|
@bbakerman agreed, I'll split this PR in 2 so we can have both at the same time. Edit: added back |
@experimental_disableErrorPropagation with onError parameteronError request parameter
I'm opening this as a heads up: see graphql/graphql-spec#1163
Not sure we want to merge is now since it's not in graphql-js yet and the
@experimental_disableErrorPropagationdirective still gets the job done for now. But looks like this is the direction we're taking.