Resolve dot-relative Markdown links from source files#459
Open
Entr0zy wants to merge 1 commit into
Open
Conversation
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
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
/claim #274
This updates Markdown link resolution so dot-relative paths are resolved from the Markdown file containing the reference instead of being treated as workspace-root-relative. That allows nested files to resolve links such as
./targetand../targetagainst nearby notes while preserving existing root-relative behavior for paths likefolder/file.Changes
./and../link targets relative to the source file parent before comparing them with indexed vault paths.Verification
git diff --checkpassed.cargo testin this local environment because Cargo is not installed here (spawnSync cargo ENOENT).