Refine the warnings about incompatible linter options

[MichaReiser]

Summary

Avoid warning about incompatible rules except if their configuration directly conflicts with the formatter. This should reduce the noise and potentially the need for #8175 and #8185

I also extended the rule and option documentation to mention any potential formatter incompatibilities or whether they're redundant when using the formatter.

• LineTooLong: This is a use case we explicitly want to support. Don't warn about it
• TabIndentation, IndentWithSpaces: Only warn if indent-style="tab"
• IndentationWithInvalidMultiple, IndentationWithInvalidMultipleComment: Only warn if indent-width != 4
• OverIndented: Don't warn, but mention that the rule is redundant
• BadQuotesInlineString: Warn if quote setting is different from format.quote-style
• BadQuotesMultilineString, BadQuotesDocstring: Warn if quote != "double"

Test Plan

I added a new integration test for the default configuration with ALL. ruff format now only shows two incompatible rules, which feels more reasonable.

[MichaReiser]

Current dependencies on/for this PR:

• main
  • PR Refine warning about incompatible isort settings #8192
    • PR Refine the warnings about incompatible linter options #8196 👈
      • PR Don't warn about magic trailing comma when isort.force-single-line is true #8244

This comment was auto-generated by Graphite.

[MichaReiser]

I'm undecided if we should warn about this rule. The formatter might collapse implicit string concatenated lines which then triggers this rule. However, it might be something users want to fix manually.

Same for MissingTrailingComma. The rule might require manual intervention (and magic-trailing-comma set to respect), but once fixed it remains fixed.

[yakMM]

If the formatter collapses the strings, I would love to know about it to fix it afterward.

[github-actions]

PR Check Results

Ecosystem

✅ ecosystem check detected no changes.

[yakMM]

Looks great, most of my warnings are gone!

[MichaReiser]

yakMM wrote

Tested on my project, only have a warning about ISC001 and isort.split-on-trailing-comma left. I will reply to your comment about this one directly in the PR.

Don't know if I should open a new issue, but I feel like the warning about isort.split-on-trailing-comma=false is underserved since I already have isort.force-single-line=true, so that isort.split-on-trailing-comma=false will never be applied. I don't know how complicated it is to keep making exceptions to the warning on the implementation side.

[charliermarsh]

I these think these are redundant when using tabs in the formatter.

[charliermarsh]

This was removed because the formatter will never output code that triggers it? Is that right?

[charliermarsh]

Yes, I believe this is the case.