-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Please exports your errors type #182
Comments
Do not rely on the |
fastify/fastify-error#86 (comment) is supposed to be the best solution
But that doesn't really help with |
Hi @FrancoRATOVOSON, is this still an issue? We've obviously released Fastify v5 since this was opened. |
@Fdawgs Yes, but it seems that you didn't plan to export those error type. |
Prerequisites
🚀 Feature Proposal
I have my custom way to handle errors depending on their type. I know that by using
verifyBearerAuth
there are 2 types of errors that can be thrown and I have a custom way to handle booth cases separately. But now I cannot check if the error is anFST_BEARER_AUTH_INVALID_AUTHORIZATION_HEADER
or anFST_BEARER_AUTH_MISSING_AUTHORIZATION_HEADER
because none of them is exportedMotivation
Handling errors a custom way.
Example
The text was updated successfully, but these errors were encountered: