Skip to content

Comments

Wikilink import pathing#800

Closed
trangdoan982 wants to merge 1 commit intomainfrom
cursor/ENG-1450-wikilink-import-pathing-750d
Closed

Wikilink import pathing#800
trangdoan982 wants to merge 1 commit intomainfrom
cursor/ENG-1450-wikilink-import-pathing-750d

Conversation

@trangdoan982
Copy link
Collaborator

Translate all wikilinks in imported notes to relative paths within the import/{vaultName}/ directory.

Previously, wikilinks that were not assets were not imported with relative paths. This led to issues where clicking on such a link would create a new file in the root folder of the imported vault, rather than within the designated import/{vaultName}/ structure. This PR ensures that all wikilinks resolve correctly to their intended location within the imported vault, maintaining organization and preventing incorrect file creation.


Linear Issue: ENG-1450

Open in Cursor Open in Web

- Updated updateMarkdownAssetLinks to handle non-asset wikilinks
- Non-asset wikilinks are now rewritten to point to import/{spaceName}/ directory
- This ensures files created by clicking wikilinks are placed in the correct location
- Resolves relative wikilinks based on original note path before rewriting

Fixes: ENG-1450

Co-authored-by: Trang Doan <trangdoan982@users.noreply.github.com>
@cursor
Copy link

cursor bot commented Feb 17, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@linear
Copy link

linear bot commented Feb 17, 2026

@supabase
Copy link

supabase bot commented Feb 17, 2026

This pull request has been ignored for the connected project zytfjzqyijgagqxrzbmz because there are no changes detected in packages/database/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@trangdoan982 trangdoan982 deleted the cursor/ENG-1450-wikilink-import-pathing-750d branch February 21, 2026 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants