Fix: boolean casting #195
Open
Fix: boolean casting #195
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
fix: correctly validate "falsey" not null parameters values
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.
This PR fixes two issues related to request validation.
If a parameter is not null but "falsey" such as
0the parameter it is not validatedthis PR corrects this and updates the tests
It is currently not possible to validate "boolean" type parameters as the assertion will always fail since the string type value from the request parameter is not cast to boolean.
The data (string) must match the type: booleanThis PR casts
trueandfalsestring values only to the appropriate boolean, and adds test coverage