Skip to content

Split mccabe --max-complexity into its own extension section - #11341

Open
SemTiOne wants to merge 3 commits into
pylint-dev:mainfrom
SemTiOne:docs-design-checker-9174
Open

Split mccabe --max-complexity into its own extension section#11341
SemTiOne wants to merge 3 commits into
pylint-dev:mainfrom
SemTiOne:docs-design-checker-9174

Conversation

@SemTiOne

Copy link
Copy Markdown

Type of Changes

Type
📜 Docs

Description

Two checkers share name = "design", so --max-complexity merged into the standard Design section. The collision is static (one extension reuses a core name), so we hardcode frozenset({"design"}) instead of spawning linter instances to detect it. An optional options_anchor kwarg on BaseChecker.get_full_documentation() lets the doc generator pass the correct anchor; callers that don't pass it keep the old behavior.

Closes #9174

@SemTiOne
SemTiOne force-pushed the docs-design-checker-9174 branch from d4a9d16 to 66c3c58 Compare August 25, 2026 02:58
@SemTiOne
SemTiOne force-pushed the docs-design-checker-9174 branch from 6cd9a9d to 7e0e776 Compare August 25, 2026 03:35
@SemTiOne
SemTiOne marked this pull request as ready for review August 25, 2026 03:39
@SemTiOne

Copy link
Copy Markdown
Author

When I look at it again, I shouldn't hardcode frozenset({"design"}). I'll replace it with collision detection computed from the registered linter (_colliding_checker_names) so that any future core/extension name clash is handled automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Better docs required for 2 'design' checkers

1 participant