Fix stepper heading levels from snippets #2436
Merged
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.
Closes #2434
Problem
Stepper steps in included snippets always appeared as
h2in the table of contents, regardless of the parent document's heading structure.Solution
When processing included snippets, we adjust stepper step heading levels based on the preceding heading in the parent document. Stepper steps that defaulted to
h2are adjusted to be one level deeper than the preceding heading.Example:
Stepper steps now correctly become
h3instead ofh2.Changes
IsStepperStepflag to distinguish stepper steps from regular headings