Fix/exact text matching empty target - #2882
Open
Joel (aspire488) wants to merge 2 commits into
Open
Joel (aspire488) wants to merge 2 commits into
Joel (aspire488) wants to merge 2 commits into
Conversation
This branch has not been deployed
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
1 participant
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
Tests and Documentation
Description
Fixes an edge case in "ExactTextMatching" where an empty or whitespace-only target could incorrectly produce a match.
Python treats an empty string as being contained in every string (""" in text"), so an empty target could result in a false positive. This is particularly relevant when matching values that may default to an empty string.
Changes
Related Issue
Closes #2881
Validation
Added unit tests covering:
Non-empty matching behavior remains unchanged.