[BUG][code-analyzer] Disabled rules are moved to the end of the config file rules list

[dschach]

Have you tried to resolve this issue yourself first?

• I confirm I have gone through the above steps and still have an issue to report.

Bug Description

I disabled some rules and recreated the config file. ( see #2013 )

All the disabled rules were moved to the end of the pmd section.

But I want to view ALL the PMD rules alphabetized so I know which ones are in there.

Output / Logs

Steps To Reproduce

1. Disabled a rule with disabled: true
2. Run echo 'y' | sf code-analyzer config --include-unmodified-rules --rule-selector all --config-file code-analyzer.yml --output-file code-analyzer.yml
3. See that the disabled rules are moved.

Expected Behavior

All rules should be alphabetized by their unique key. This extra sort doesn't help anything and only can confuse people.

Operating System

macOS

Salesforce CLI Version

@salesforce/cli/2.128.5 darwin-arm64 node-v22.22.1

Code Analyzer Plugin (code-analyzer) Version

5.11.1

Node Version

No response

Java Version

No response

Python Version

No response

Additional Context (Screenshots, Files, etc)

This is actually a significant bug because changing from expected behavior will confuse people.

Workaround

No response

Urgency

Moderate

[namrata111f]

@dschach I did not get the issue exactly. Previously the rules were not alphabetized but rather were in the order their engine returned them in. Do you want that order to be preserved? Disabled rules are not returned from engine anymore hence moving them at the end in user config.

[namrata111f]

Have checked with the team on this. We will address the issue and tracking via work item.

[git2gus]

This issue has been linked to a new work item: W-21883400