Deactivate obsolete rules by default

[picpicpic]

Is your feature request related to a problem? Please describe.
Lot of rules are based on 3rd edition which no longer exist in 4 edition (we are currently in the 5th edition)
Some of them are bad practices ( ie : GCI67 i++ versus ++i )

Describe the solution you'd like
Obsolete rules must deactivated when the plugin is installed/updated

Describe alternatives you've considered
We can't use the plugin with those default rules

Additional context

[dedece35]

Hi @picpicpic
thank you for this issue.

I don't understand your request because when you install one creedengo plugin, rules are all available (with tag "creedengo" for example) but there is no default quality profile created with creedengo rules. After creedengo plugin installed, you must create a new profile with creedengo rules enabled, or you must upgrade an existing quality profile to add creedengo rules.
Thus, by default, there are no creedengo rules enabled.

Can you give some more information about your contexte, or your tests ?

[picpicpic]

Hi @dedece35

Thank you for your question.

What I meant is that the Creedengo rule set currently contains a mix of relevant rules and others that are outdated or questionable. This creates a need for manual filtering, which is left to the person installing the plugin or configuring SonarQube.
From my experience, these users often do not have the necessary expertise to make such distinctions, and therefore tend to enable all rules by default. This promote poor practices (ie : GCI67 recommending i++ versus ++i), and lead to confusion.

In our case, teams are generally not aware of these nuances, which results in recurring and unproductive debates.

I would expect obsolete or controversial rules to be clearly deprecated and eventually removed from the plugin, in order to provide a more reliable and curated default rule set.