smallrye-graphql: Improve error mapping (client)
Currently, when there is an error response, a GraphQlClientException is thrown with the error list in the message… as a String.
- 1. Make the full error structure available to an exception handler.
- 2. Allow for a field in the expected result to contain error results (e.g. for partial results).
- 3. Introduce an error mapper that can throw specific exceptions derived from the errors received.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 15
Commits related to this issue
- fix #167: improve client error handling; log request/response at debug, not info Signed-off-by: Rüdiger zu Dohna <snackbox@sinntr.eu> — committed to t1/smallrye-graphql by t1 6 years ago
- fix #167: improve client error handling; log request/response at debug, not info Signed-off-by: Rüdiger zu Dohna <snackbox@sinntr.eu> — committed to t1/smallrye-graphql by t1 6 years ago
- Merge pull request #505 from t1/167-client-error-handling fix #167: improve client error handling — committed to smallrye/smallrye-graphql by phillip-kruger 6 years ago
That would be cool. Could you just hold your feet still just a little longer until I’ve added the other variant, as we will get into merge conflicts otherwise?