Output lint codes instead of RuleTable?

[jorgegomezcq]

Hi,

I'm able to output the pydocstyle rules that are in effect for a given configuration file and path foo with ruff check --show-settings foo/ but is there a way to just output the pydocstyle official codes? For example, instead of FitsOnOneLine I'd prefer to see a simple table saying that D200 is enabled, etc.

Idea: ruff --show-enabled-codes --config ruff.toml or similar.

$ ruff check --show-settings foo/ --config ruff.toml
Resolved settings for: "/home/bar/foo/"
Settings path: "/home/bar/foo/ruff.toml"
Settings {
    rules: RuleTable {
        enabled: {
            FitsOnOneLine,
            NoBlankLineBeforeFunction,
            NoBlankLineAfterFunction,
            IndentWithSpaces,
            UnderIndentation,
            OverIndentation,
            NewLineAfterLastParagraph,
            BlankLineBeforeClass,
            SectionNotOverIndented,
            TripleSingleQuotes,
            EscapeSequenceInDocstring,
            NoSignature,
            FirstLineCapitalized,
            CapitalizeSectionName,
            NoBlankLineAfterSection,
            NoBlankLineBeforeSection,
            BlankLinesBetweenHeaderAndContent,
            EmptyDocstringSection,
            SectionNameEndsInColon,
            OverloadWithDocstring,
        },
        should_fix: {
            FitsOnOneLine,
            NoBlankLineBeforeFunction,
            NoBlankLineAfterFunction,
            IndentWithSpaces,
            UnderIndentation,
            OverIndentation,
            NewLineAfterLastParagraph,
            BlankLineBeforeClass,
            SectionNotOverIndented,
            TripleSingleQuotes,
            EscapeSequenceInDocstring,
            NoSignature,
            FirstLineCapitalized,
            CapitalizeSectionName,
            NoBlankLineAfterSection,
            NoBlankLineBeforeSection,
            BlankLinesBetweenHeaderAndContent,
            EmptyDocstringSection,
            SectionNameEndsInColon,
            OverloadWithDocstring,
        },
    },

[MichaReiser]

Not an answer to your question, but this is related to #8334

[jorgegomezcq]

Thanks for linking the issue.