feat(forms): handle string with and without line boundary on pattern validator #19256
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Validator pattern only works with string without line boundaries (
^
&$
), the validator will then add them itself to the string automatically. But today wasn't the first time I helped someone because those boundaries characters were already present on the string and so the validator was failing.Issue Number: N/A
What is the new behavior?
I think we can be a bit smarter here and only add those boundaries characters if they're missing.
It's easy enough and has no impact.
Does this PR introduce a breaking change?
Other information