We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I was interested into integrating the error format as the RFC specification 7807 that basically is a standard format to return errors on an REST API. If you find it interesting we could have a discussion on how to implement this (maybe that would be just an extension/optional feature). In the link below you can find some more info about it: https://www.linkedin.com/pulse/rfc-7807-error-handling-standard-apis-david-rold%C3%A1n-mart%C3%ADnez#:~:text=The%20purpose%20of%20the%20specification,%3F%20%5B%20reference%20in%20resources%5D).
The text was updated successfully, but these errors were encountered:
Duplicate of #170
Sorry, something went wrong.
No branches or pull requests
Hi,
I was interested into integrating the error format as the RFC specification 7807 that basically is a standard format to return errors on an REST API. If you find it interesting we could have a discussion on how to implement this (maybe that would be just an extension/optional feature).
In the link below you can find some more info about it:
https://www.linkedin.com/pulse/rfc-7807-error-handling-standard-apis-david-rold%C3%A1n-mart%C3%ADnez#:~:text=The%20purpose%20of%20the%20specification,%3F%20%5B%20reference%20in%20resources%5D).
The text was updated successfully, but these errors were encountered: