Request: allowlist of codes for RUF100 not to autoremove

[jamesbraza]

Some tools like to use flake8 as a vehicle for config files and ignores:

• https://github.com/jsh9/pydoclint
• https://github.com/andreoliwa/nitpick

However, RUF100 in ruff==0.1.1 is removing the # noqa's I add for those tools.

Any chance we can a new config option for ruff that is basically an allowlist override for RUF100?

[jamesbraza]

I guess a workaround is, for each noqa that is being removed by RUF100, I can do # noqa: DOC501,RUF100

[charliermarsh]

I think we have a setting for this: https://docs.astral.sh/ruff/settings/#external. Codes marked as external won’t be removed and flagged by RUF100 (or at least, they shouldn’t be).

Mind giving that a try?

[jamesbraza]

Thanks for the response!

I am using pydoclint, which has DOC error codes: https://github.com/jsh9/pydoclint#3-style-violation-codes

external does work, though you have to specify the exact code. It would be nice to be able to use external = ["DOC"], as opposed to external = [..., "DOC201", "DOC301", ..., "DOC501"]

This leads me to a few requests:

• Document external setting in https://docs.astral.sh/ruff/rules/unused-noqa/
• (there is a broken link at the bottom of https://docs.astral.sh/ruff/rules/unused-noqa/)
• Allowing external to use rule prefixes (e.g. DOC instead of DOC501)

Let me know what you think

[zanieb]

Fixing those issues in #8171 and #8172

[jamesbraza]

Thank you! Interested in hearing what you think of moving external to work using prefixes of rules, not just exact matches

[charliermarsh]

I think matching prefixes is pretty reasonable.

[jamesbraza]

Thank you and cool! I opened #8174 for that.

Will leave this open for @zanieb 's two docs PRs to close this one out ✅ .