We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have found that both rules are checking that the key is present in the dict under validation.
My opinion is that :
required
exists
If you agree with that I'll open a PR to update that, but that's a breaking change I guess.
The text was updated successfully, but these errors were encountered:
Plus to this quote:
required: value must be there and not null (null here can be considered with truthy meaning)
I'm trying some tests here and when validate against required rule, even if input are in request, it can be empty like that:
{"name" : ""}
Then the required rule should not passes, but actually it pass as correct.
Sorry, something went wrong.
@Marlysson Yes indeed, thanks for reporting this.
I fixed this in PR #44, we will merge for Masonite 3.0 I guess 😉 .
Fixed in #44
No branches or pull requests
I have found that both rules are checking that the key is present in the dict under validation.
My opinion is that :
required
: value must be there and not null (null here can be considered with truthy meaning)exists
: value must exists in the dictionary (but can be null)If you agree with that I'll open a PR to update that, but that's a breaking change I guess.
The text was updated successfully, but these errors were encountered: