We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey there, since the new Version 0.32 we get many false positive if a dot . is included in the filter string if you use SetRange().
.
SetRange()
It would be awesome if this problem is fixed with the next version. Thanks!
The text was updated successfully, but these errors were encountered:
It seems I've introduced a bug during rework on this rule, oops!
I believe I've resolved this in the Pre-release v0.32.1 version of the LinterCop. Could you verify if it now works as expected?
Sorry, something went wrong.
Yeah, with the prerelease version it works again as expected 👍 Thansk!
Version v0.33.0 of LinterCop has been released as the latest update.
Arthurvdv
No branches or pull requests
Hey there,
since the new Version 0.32 we get many false positive if a dot
.
is included in the filter string if you useSetRange()
.It would be awesome if this problem is fixed with the next version. Thanks!
The text was updated successfully, but these errors were encountered: