After upgrading to 6.2, in the hope it would fix the above issue, the SonarLint extension in my VS Code now reports 0 errors for all of my files… which just is not correct (it just cannot be ).
In other words: the function which was completely underlined and reason to write issue 18474 became completely issue-free after upgrade to 6.2.
So something seems wrong, either with my configuration, or with the updated plugin. Any ideas?
Here is the SonarLint output of VS Code:
[Info - 10:29:21.224] Downloaded plugin list in 68ms
[Info - 10:29:21.267] Downloaded settings in 43ms
[Info - 10:29:24.698] Using storage for server '[redacted]' (last update 2/19/20 10:29 AM)
[Info - 10:29:25.087] Downloaded settings in 120ms
[Info - 10:29:27.180] Downloaded settings in 42ms
[Info - 10:29:29.452] Analyzing file 'file:///redacted/path/to/file1.js'...
[Info - 10:29:31.194] Found 0 issue(s)
[Info - 10:29:31.195] Analyzing file 'file:///redacted/path/to/file2.js'...
[Info - 10:29:32.354] Found 0 issue(s)
hi @Quentin thanks for the hint – in fact, deactivating S124 worked like a charm!
sonarlint now displays a lot of issues for the files again (nothing to be surprised of). and issue 18474 is fixed, too! yay!
however, i think there still is room for improvement regarding the underlining of functions with other issues. gonna check if corresponding issues already exists and will add new ones if not.