Add Option to generate Obsidian URLs in Landmark Subdirectories #104
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.
Apologies for the title, but I'm having trouble succiently describing it.
I like how Waypoint automatically generates a Table of Content, but unfortunately it links sub-sub-directories with the top directory. Of course I could place Waypoints and sever the links, but it diminishes the Table of Contents aspect a bit. I did a little research and to my understanding there seems to be only one way to link to another file without connecting them on the graph:
obsidian://open?vault=[VAULT NAME]&file=[FILE NAME]
.Quickly hacked something together. Added another bool to
getFileTreeRepresentation
that defaults to false. During thefolderNote
section, if the setting is enabled and a landmark is in the file, set bool to true, and subsequent recursions will generate the Obsidian URL instead of MD/Wiki Links.Results are a graph that looks identical to one with sub-directory Waypoints and table of contents that is close to one without sub-directory Waypoints, the difference beings the links. Functionally close to a MD/Wiki Link except no middle clicking new tab, dragging to tab, and likely other convenience features that come with native links. Settings description could probably use some work.
Breaks your portable "rule" in the README, so I would understand if this were rejected. Links useless if moved out of current vault/need to be regenerated.
Child 1 & 2 are using Landmarks, Child Waypoint is using a Waypoint. Based off brief testing I don't think I broke anything.
Landmarks themselves still generate MD/Wiki Links, its just higher level Waypoints don't.