feat: require double curly braces for placeholders in regex_match
rule
#9597
+69
−4
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.
Description
This PR updates the validation behavior for the
regex_match
rule to require double curly braces{{...}}
for placeholders instead of single ones{...}
.Using single braces for placeholders conflicts with valid regex syntax, such as quantifiers (
{1,3}
), which can lead to invalid regex patterns and hard-to-debug validation issues.What changed:
regex_match
now requires{{value}}
{value}
will no longer be parsed withinregex_match
Fixes #9596
Checklist: