Link parser #1
Open
Link parser #1
Conversation
This file contains 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.
Initial version of the Obsidian Link Parser.
It maps the Obsidian references to a page with the page path, and replaces it with a relative page link.
Known Issues:
/.This happens in Obsidian when there's two files with the same name in different folders (
ExampleandResources/Example), to specify the page you want to link ([[Example]]or[[Resources/Example]])I have to review the project structure, and make it all dependent of
settings.jsfile, instead of passing configs through functions. This will improve readability, and will add cohesion to the library.I have a test deploy (https://carlos-hernandez-1.gitbook.io/untitled/empezar) with a pretty complex Obsidian Vault (https://github.com/recursosdisenoes/recursos-diseno-es/) so I can test that everything works as expeced.
In case you find something wrong there, let me know in this PR.
I will try to fix the known issues list before merging this.