Add error handlers #23
Merged
Conversation
This file contains 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
makes response types not arbitrary. Users can no longer pass whatever status with whatever bodies
Allows specifying one level of nesting when defining the routing object
Add an example of how to use nested/prefixed routes
No longer allow an empty array to be passed to the handler parameter
* docs(create-api): add internal docs to interfaces * fix(index): remove exported 'createApi' function this function is internal only and there's no need to export it * docs(create-app): add internal docs * feat(error-handler): add erorr handlers for specific routes add the possibility of the user passing an error handler function to deal with an specific route in the end of the handlers array as a new property * feat(error-handler): add global property for error handlers allow the user to override the default error handler with their own error handler middleware * fix(create-app): fix global error handler type global error handler should be of the same type as the express error handler * test(create-app/error-handlers): add tests to global and local error handlers
Signed-off-by: Lucas Santos <[email protected]>
github-actions bot
pushed a commit
that referenced
this pull request
Mar 30, 2024
# [6.3.0](v6.2.0...v6.3.0) (2024-03-30) ### Features * Add error handlers ([#23](#23)) ([ef423c8](ef423c8))
|
🎉 This PR is included in version 6.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
makes response types not arbitrary. Users can no longer pass whatever status with whatever bodies
feat(openapi): support zod openapi extension
docs(openapi): improve docs
feat(createapi): add support for nested routes
Allows specifying one level of nesting when defining the routing object
Add an example of how to use nested/prefixed routes
No longer allow an empty array to be passed to the handler parameter