(SonarQube 8.9LTS, Scanner 4.7)
We are trying to analyze a project and it is failing due to an already deactivated rule (which is deprecated).
This rule doesn’t exist in the default Quality Profiles that are being used. Can you please help with removing this rule from the analysis?
Hey there.
This security hotspot is raised by typescript:S4784, not typescript:2631. The former should be the one removed from your Quality Profile.
typescript:S4784 rule is deprecated, I already deactivated all deprecated rules. But still when the project builds this rule is affecting.
Based on the screenshot, that rule is still active in NEER way – because it inherits from the unfortunately named “Sonar Way Recommended” Quality Profile. This profile will actually no longer be included in new v9.x instances – you can read more about why here:
This means that for the time-being – I would recommend inheriting from the “Sonar Way” instead (for reasons noted in the above post), or copying your Quality Profile so that it no longer inherits from Sonar Way Recommended if you can’t change so easily (this would mean you’d be able to deactivate the rule)
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.