Stéphane Épardaud
Stéphane Épardaud
@gytis this is what @geoand talked to you about.
Excellent!
https://github.com/quarkusio/quarkus-quickstarts/pull/809/files#diff-568cb5a2fe72fb07ec9f5b4b90618a6af7cc6ffa2b8061ff715476091a16d085R108 has a pretty common error handler that produces: ```json { "exceptionType": exception.getClass().getName(), "code": statusCode, "error": exception.getMessage() } ``` while the RFC is more: ```json { "type": "https://example.com/probs/out-of-credit", "title": "You...
I can't find anything in the react docs about error format either. Do @phillip-kruger or @ia3andy have any knowledge about this?
Thanks, it's good to know it exists, and perhaps we should point our users to it if they need custom problem responses. But I don't think we need this ourselves...
For extra detail, sure, but this should be the correct error body even for other errors if the clients wants JSON or if the response type is JSON.
Oh, XML, sure why not. I forgot it existed ;)
That looks nice, but I'm not sure if this should really live outside of quarkus itself. I mean: I don't see why most users would want to opt out of...
Well, yes, it sounds like this could be a new core extension that both resteasy versions import by default, no?