Status length validation spec updates #30132
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.
This is a slightly different approach to the spec portion of #30091
I think in theory that other could be rebased against this and remove all it's spec changes and be reviewed just on the merits of the configurability.
Separately, I noticed while in here we sort of have a mix of styles in validator specs, with some doing this stub out of the activemodel errors object, and some doing a (what I think is preferred) more native usage of the validator via an in-spec class. Might do a round of updating there to align them all style wise to that latter approach.