Elena Vilchik
Elena Vilchik
https://frontendgirl.com/spring-cleaning-how-to-safely-remove-dead-code-unused-exports-in-js-codebase/
Similar rules is implemented for CFamily https://sonarsource.github.io/rspec/#/rspec/S5536
"Return values from functions without side effects should not be ignored" triggering on `Array#find`
Hi, Your code could be refactored to avoid changing variable from outer scope: ``` const found = Object.entries(haystack).find(([key, arr]) => { return arr.find(obj => obj.name === needle); }); if (found...
Removing from MMF as we didn't have time for it
https://community.sonarsource.com/t/await-should-not-be-used-redundantly-affecting-stacktraces/44531
Reported in https://community.sonarsource.com/t/sonarlint-gives-warning-for-contradicting-rules/50960/5
Reported in https://community.sonarsource.com/t/rule-falsely-claims-dissimilar-types-when-they-might-match/56330
@robertpatrick Please open a new issue with the code examples reproducing false positive issues you are experiencing, it will help us improve the rule
@robertpatrick are you using latest SonarLint? This rule should not be able anymore to report anything in JS files as typing information is not reliable. Due to this change https://github.com/SonarSource/eslint-plugin-sonarjs/pull/273/files#diff-49f8e5bce4cd48e0b28f0d1b7596880ce014bb8f961cfd23107279442e6fe144R29
@robertpatrick are you using connected mode (is your SonarLint connected to SonarQube or SonarCloud)? which version of SonarLint are you using?