Add max-nesting-depth rule to enforce code readability#8
Merged
Conversation
Implements a new ESLint rule that enforces maximum nesting depth for control structures (if, for, while, switch, try, etc.). Deep nesting makes code difficult to read and maintain. Features: - Configurable max depth (default: 3) - Functions reset nesting depth (encourages extraction) - Optional IIFE handling with ignoreTopLevelIIFE option - Comprehensive test coverage with 24 test cases This rule complements existing rules like no-complex-conditionals and low-function-cohesion to promote maintainable, readable code.
aryelu
force-pushed
the
claude/eslint-rules-review-hkDSR
branch
from
40a07b1 to
e4c7f46
Compare
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
2 participants
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.
Implements a new ESLint rule that enforces maximum nesting depth for
control structures (if, for, while, switch, try, etc.). Deep nesting
makes code difficult to read and maintain.
Features:
This rule complements existing rules like no-complex-conditionals and
low-function-cohesion to promote maintainable, readable code.