The PR with the change in the naming comparison was released in version 9.18 of our analyzer. This version will be included in the next upcoming releases of SonarLint and SonarQube. @OddMathisenNOV can you try the new version once the release of SonarLint/SonarQube is done?
Do note that my version of the SonarLint extension does not correspond to the 10.4 version of SonarQube (Currently at 184.108.40.206110). Is there any reference to which version of SonarQube corresponds to which version of the SonarLint 2022 extension in VisualStudio?
If not, will it just be the next minor update, so 7.6.x?
Do you use SonarQube or SonarCloud? Depending on which, I can tell what version of the analyzer you are likely using. The fix will be part of the SonarQube 10.4 release, which is scheduled for the near future. SonarCloud uses version 9.19 of the analyzer as of now.
Please keep in mind that SonarLint comes with its own version of the analyzer, but when used in connected mode, it downloads the analyzer from the server (this is to make sure the same version is used in SonarLint and CI).
We are using SonarCloud. I do not understand how the different versions map up and was basing the 10.4 version on the 9.18 release notes, assuming this would somehow translate to SonarCloud and, in turn, the connected linter.
If SonarCloud is on v9.19 of the analyzers and our linter is in connected mode, we should not have this issue, correct?