Fix Pattern message formatting with range quantifiers#36832
Open
Will-thom wants to merge 1 commit into
Open
Conversation
Signed-off-by: Will-thom <116388885+Will-thom@users.noreply.github.com>
spring-projects-issues
added
the
status: waiting-for-triage
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.
Closes gh-21750
This updates Bean Validation error adaptation so Spring-style default messages such as {0} must match {regexp} can still be rendered with MessageFormat after Bean Validation has interpolated a constraint attribute containing regex braces, for example \d{1,3}.
The change escapes interpolated constraint attribute values before default-message rendering and stores the render decision in the serializable Spring error type so deserialized errors behave consistently.
Tests:
Note: local machine has JDK 21 only; Spring main currently requires a Java 25 toolchain, so the focused test was run with a temporary local toolchain override that was not committed, excluding the Java 24 multi-release compile task.