Adjusting the Quality Profile assigned to your project is the tried and true (and built-in) method to define the rules you want to apply to your project. Anything else would be a painful workaround as new rules are regularly being added to the default Quality Profile, and it’s not possible to exclude an entire rule type.
Can you discuss a bit more why you want to turn off Code Smells completely? Are they irrelevant? Duplicating issues already raised by ESLint?
Adjusting the Quality Profile assigned to your project is the tried and true (and built-in) method to define the rules you want to apply to your project. Anything else would be a painful workaround […]
Could you please elaborate on this? I can’t seem to adjust the built-in profile, so I’m forced to make a copy, which comes with the problem you also mentioned about not inheriting new rules.
Can you discuss a bit more why you want to turn off Code Smells completely? Are they irrelevant? Duplicating issues already raised by ESLint?
Yes, they are either duplicating our ESLint rules or are not relevant for us. We want to have ESLint as the source of truth for assessing code quality, including security, but want to use Sonar as a dashboard to monitor only security issues across the entire company.