Failing test to demonstrate problem with detecting regex match calls in Ruby #13748
+7
−0
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.
This PR just demonstrates a problem with the current implementation of
IncompleteHostnameRegExpfor Ruby. Specifically, it seems that the rule with report false positives for anyX.match(Y)method call whereYis aStringandXis any object with amatchmethod.In the example in this PR, we define a new class
ClassWithMatchwith amatchmethod, and call it with:Running tests then reports this:
Notice the reported problem:
So, the rule incorrectly thought that the string
"http://docs.github.com/"was a regex being used for matching, likely because in Ruby'sStringclass has amatchmethod which takes aStringparameter for defining the regex:https://ruby-doc.org/3.2.2/String.html#method-i-match