docs: clarify entry hints share one approach direction, unlike exit - #1632
Open
pinin4fjords wants to merge 3 commits into
Open
docs: clarify entry hints share one approach direction, unlike exit#1632pinin4fjords wants to merge 3 commits into
pinin4fjords wants to merge 3 commits into
Conversation
Entry and exit directives were documented together as if both support per-line divergent sides. Only exit does; a section has a single entry approach direction, so entry: <side> | <lines> sets one shared side for the whole section rather than carving out an independent side for the listed lines.
Contributor
|
Render preview is ready for review: This preview shows only the renders that changed compared to |
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
1 participant
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.
Summary
entry: <side> | <lines>sets one shared side for the whole section rather than an independent side for the listed lines.Prompted by #1629, which was closed as working-as-intended but highlighted that the docs read as if entry supported the same per-line flexibility as exit.
Test plan