-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
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
Implement RFC7807 #64
Labels
enhancement
New feature or request
Comments
This would be interesting. It might be too late for Fastify v4 but would you like to assemble a PR anyway? |
Is fastify-error the right place? Or should it be done in a different place? |
It should be done both here and in Fastify |
Closed
Reopening for #119 |
How about we ads a new factory for RFC7807 errors? |
Seems like a good solution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
🚀 Feature Proposal
We could implement a toRFC7807-method, which creates RFC7807-compatible JSON Response to FastifyError and use it in fastify 4 by default.
So we could create a new Error like this
and then the resulting JSON would be:
Motivation
No response
Example
No response
The text was updated successfully, but these errors were encountered: