Improve docs on regex filters #67133
Open
+28
−4
Conversation
This file contains 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
When capture groups are not used, the filter will always return something that will always evaluate as boolean False (because lack of capture groups means an empty tuple is returned for regex matches). This commit improves the docs, clarifying this and recommending how to use this filter to correctly identify if the pattern matched.
twangboy
approved these changes
Jan 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When capture groups are not used, the filter will always return something that will evaluate as boolean False (because lack of capture groups means an empty tuple is returned for regex matches). This commit improves the docs, clarifying this and recommending how to use this filter to correctly identify if the pattern matched.