feat: export httpErrors#148
Merged
Merged
Conversation
arthurfiorette
force-pushed
the
master
branch
from
4584cce to
5041f90
Compare
Contributor
Author
|
Ready for review :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These errors already can be used with
fastify.httpErrors, however, when writing util functions or functions that will endup inside a route call but are elsewhere, passing thefastify.httpErrorsas parameters throughout multiple functions is bad. It is already exported fromlib/httpErrors, this PR just add their types and the index.jshttpErrorsexport.Test for types and js were added.
Checklist
npm run testandnpm run benchmarkand the Code of conduct