Fix bare-path guard to exclude single-segment sibling references - #24
Merged
Conversation
Single-segment bare paths like "page-b.md" are sibling-file references that need normalizePath() to resolve. The bare-path pre-normalization check now requires at least one "/" to distinguish repo-root-relative paths (docs/markdown/autoapi/foo/) from sibling references. Bumps version to 0.14.4.
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
page-b.mdare sibling-file references that neednormalizePath()to resolve correctly/to distinguish repo-root-relative paths (docs/markdown/autoapi/foo/) from sibling references.md-stripping global mappingsTest plan
page-b.md#sectionresolves via sourceToTargetMap (not early-returned)/are unaffected)./and../regression tests still passtsc --noEmitclean