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
Is your feature request related to a problem? Please describe.
The current version of the error handling of the TOMP API seems to be oriented towards RFC 7807 in terms of style. However, it is not clear from the documentation if it is based on the standard or if this is more of a coincidence.
Urgency
Minor
The work on version 2.0 would be an opportunity to check this. Aligning with RFC 7807 could improve interoperability and adherence to established standards.
Additional context
RFC 7807 is a widely adopted standard for error handling in APIs. Including a reference to it or aligning with it more closely could benefit the API's usability.
Describe the solution you'd like
A clear review and alignment of TOMP-API error handling with RFC 7807, or documentation on why deviations are necessary.
Describe alternatives you've considered
Maintaining the current structure but adding a note in the documentation about the deviations from RFC 7807.
Possible Implementation
For 2.0 - review the current error handling structure, compare it with RFC 7807, and adjust the fields as necessary to ensure compliance or provide clear documentation on the chosen approach.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current version of the error handling of the TOMP API seems to be oriented towards RFC 7807 in terms of style. However, it is not clear from the documentation if it is based on the standard or if this is more of a coincidence.
Urgency
Minor
The work on version 2.0 would be an opportunity to check this. Aligning with RFC 7807 could improve interoperability and adherence to established standards.
Additional context
RFC 7807 is a widely adopted standard for error handling in APIs. Including a reference to it or aligning with it more closely could benefit the API's usability.
Describe the solution you'd like
A clear review and alignment of TOMP-API error handling with RFC 7807, or documentation on why deviations are necessary.
Describe alternatives you've considered
Maintaining the current structure but adding a note in the documentation about the deviations from RFC 7807.
Possible Implementation
For 2.0 - review the current error handling structure, compare it with RFC 7807, and adjust the fields as necessary to ensure compliance or provide clear documentation on the chosen approach.
The text was updated successfully, but these errors were encountered: