[9.x] Add "missing" validation rules#45717
Merged
Merged
Conversation
timacdonald
changed the title
Member
|
Looks good, but needs corresponding method additions in |
Member
Author
|
Added. |
This was referenced Jan 20, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Missing is a strict version of the prohibits rule. Missing is implicit, so it runs even if the value is an empty string.
You can think of "missing" as running array_key_exists (but supporting dot notation).
Will follow up with documentation and skeleton PRs if we are happy with this one.
I have only added the permutations that I think have utility:
missingmissing_if:attribute,valuemissing_unless:attribute,valuemissing_with:attribute1,attribute2missing_with_all:attribute1,attribute2Skeleton: laravel/laravel#6078
Documentation: laravel/docs#8465