Fix URI bugs by using .obsidian instead of cache

[smartguy1196]

Use case or problem

The current implementation of path URIs doesn’t make any sense and leads to buggy behavior like the problems discussed in this thread:

Allow Obsidian URI to support vaults at different paths with the same name

Once you’ve done the above, delete everything above this line. Steps to reproduce Create a vault on C:\obsidian named “Identity” (we’ll reference this as vault1) Create a vault on D:\obsidian named “Identity” (we’ll reference this as vault2) Create a note in vault1 Create a note in vault2 drag and drop the note from vault1 to note in vault2 (to link the note in vault1 from note in vault2) Alternatively, copy obsidian URL and create the link in the note in vault2 Expected result Click t…

Proposed solution

The way that Obsidian locates vaults at the moment is by looking through Obsidian’s JSON-cache files instead of trying to locate the .obsidian folder. I understand how the JSON-cache is used for loading the correct data from Obsidian’s/Electron’s leveldbs, but this behavior isn’t always required for loading the vault.

I discuss how Obsidian does this on one of my blog posts: Unit Testing - Obisidian Plugins - smartguy1196's projects

This makes sense for the open?vault=... URIs but not for open?path=...

What would make sense would be for obsidian to locate the vault by the .obsidian folder similarly to how node.js finds the node_modules folder.

Current workaround (optional)

My method for manually adding untracked vaults somewhat fixes the issue (blog post)