Split mccabe --max-complexity into its own extension section - #11341
Open
SemTiOne wants to merge 3 commits into
Open
Split mccabe --max-complexity into its own extension section#11341SemTiOne wants to merge 3 commits into
SemTiOne wants to merge 3 commits into
Conversation
SemTiOne
force-pushed
the
docs-design-checker-9174
branch
from
August 25, 2026 02:58
d4a9d16 to
66c3c58
Compare
SemTiOne
force-pushed
the
docs-design-checker-9174
branch
from
August 25, 2026 03:35
6cd9a9d to
7e0e776
Compare
for more information, see https://pre-commit.ci
SemTiOne
marked this pull request as ready for review
August 25, 2026 03:39
Author
|
When I look at it again, I shouldn't hardcode |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of Changes
Description
Two checkers share
name = "design", so--max-complexitymerged into the standard Design section. The collision is static (one extension reuses a core name), so we hardcodefrozenset({"design"})instead of spawning linter instances to detect it. An optionaloptions_anchorkwarg onBaseChecker.get_full_documentation()lets the doc generator pass the correct anchor; callers that don't pass it keep the old behavior.Closes #9174