Cap the default block nesting level at 100 - #1136
Closed
GrahamCampbell wants to merge 1 commit into
Closed
Conversation
GrahamCampbell
force-pushed
the
cap-default-nesting-level
branch
from
August 10, 2026 15:34
d1e4762 to
96a9287
Compare
Member
|
Let's tackle this as part of #1137 instead |
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.
This is the behavior-changing alternative to #1135. It caps nesting at 100 by default, preserves intentionally deeper fixtures with explicit overrides, and documents the compatibility trade-off.