[12.x] add explanation and example for prohibited_if rule #10448
Conversation
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
… adds a clear explanation and usage example for the `prohibited_if` validation rule in Laravel 12's validation documentation. This helps developers better understand how to dynamically exclude fields from requests based on the value of another field.
… This PR adds a clear explanation and usage example for the `prohibited_if` validation rule in Laravel 12's validation documentation. This helps developers better understand how to dynamically exclude fields from requests based on the value of another field." This reverts commit 8d5a8c8.
|
This seems to already be documented? |
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 pull request adds a dedicated explanation and usage example for the
prohibited_ifvalidation rule to the Laravel 12 documentation.It helps clarify how to conditionally prohibit a field based on the value of another field, which is useful in dynamic form validation scenarios.