You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently looking into implementing error handling in asynchronous processes. I'm always in favour of using as much standardization as possible. Up until now, I was not able to find anything specific about asynchronous error handling.
Unless these details should remain domain-specific, and therefore reside only in data.
Ps: As mentioned in the RFC: Problem details are not a debugging tool for the underlying implementation;. Therefore I see a distinction between this and the already existing Severity Extension.
The text was updated successfully, but these errors were encountered:
Would it be interesting to add an RFC 9457 Problem Details for HTTP APIs inspired extension for error handling?
An example could be:
I'm currently looking into implementing error handling in asynchronous processes. I'm always in favour of using as much standardization as possible. Up until now, I was not able to find anything specific about asynchronous error handling.
Unless these details should remain domain-specific, and therefore reside only in
data
.Ps: As mentioned in the RFC:
Problem details are not a debugging tool for the underlying implementation;
. Therefore I see a distinction between this and the already existing Severity Extension.The text was updated successfully, but these errors were encountered: