fix(validation): Fix arguments validation after updating the class-validator
#1404
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
|
Agree I had to set |
|
@MedAmineFouzai You don't need to disable, you can set global options for type-graphql: |
|
I’m closing the PR due to the way to fix the issue is already exists (mentioned by MichaLytek above). Thank you! |
MichalLytek
added
Wontfix ❌
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.
In order to get rid of CVE-2019-18413 present in old versions of
class-validator. There was a bug in the old version ofclass-validator, which lead to run validation withforbidUnknownValuesenabled. So, to return the old behavior, enabling it explicitly now.