[8.x] Add prohibited validation rule #36667
Merged
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 addition to the recently added
prohibited_if
andprohibited_unless
validation rules (#36516), I think a genericprohibited
validation rule may be useful.Use case
In my specific use case, the
prohibited
validation rule is useful when building API's while working with immutable attributes, for example:The license key is immutable and for that reason it's not part of the validation rules, so the API responds with a successful status given it just ignores the
key
attribute:When working with API's this might be confusing. This might give the impression that the request was successful and both the name and key have been updated while in reality only the name has been changed. The
prohibited
validation rule will throw a validation error if a prohibited attribute is submitted.