Fix #327 and #335: break change from nest.createParamDecorator + fastify support
#336
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
…stify` support Since `@nestjs/common@9` update, throwing `HttpException` in `createParamDecorator` does not work, and just always be consired as `InternalServerException`. Therefore, every validation decorators just had thrown 500 status error instead of 400. In such reason, I've changed my custom validation decorators to send 400 status error directly through `express.Response` or `FastifyReply` instance. Also, from now on, `@nestia/core` fully supports `fastify`.
samchon
added
bug
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.
Since
@nestjs/common@9update, throwingHttpExceptionincreateParamDecoratordoes not work, and just always be consired asInternalServerException. Therefore, every validation decorators just had thrown 500 status error instead of 400. In such reason, I've changed my custom validation decorators to send 400 status error directly throughexpress.ResponseorFastifyReplyinstance.Also, from now on,
@nestia/corefully supportsfastify.