Conversation
zagushka
marked this pull request as ready for review
September 23, 2026 00:11
This branch has not been deployed
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.
What does this PR do?
Obsidian requires an escaped alias separator inside Markdown tables:
The Markdown wikilink regex currently consumes the backslash as part of the target. The extractor then looks for
notes/Target\.md, so it cannot stamp the realtarget_file. This can leave the direct and incremental extraction paths without the canonical target path.This change accepts both
|and\|as alias separators. It adds a regression test that requires both forms to resolve to the same existing Markdown file.Related to #295. This focused parser fix does not close that broader structural-extraction issue.
Type of change
How was this tested?
Graphify-specific checklist