Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat: Change Vault (Workspace) #32

Open
jbrea opened this issue Dec 31, 2024 · 2 comments
Open

Feat: Change Vault (Workspace) #32

jbrea opened this issue Dec 31, 2024 · 2 comments

Comments

@jbrea
Copy link

jbrea commented Dec 31, 2024

In obsidian.nvim there is the ObsidianWorkspace command to switch to another obsidian vault (sometimes I have also two vaults open simultaneously). For obsidian-bridge.nvim to continue functioning in the new workspace, I guess this would require changing the port number and the API key of obsidian-bridge.nvim. Is there an easy way to implement this feature?

@oflisback
Copy link
Owner

I can understand it would be neat to support something like that, would you imagine it would mirror how it's done in obsidian.nvim with something like:

  instances = {
    {
      "name": "",
      "address": ""
    },
    {
      "name": "",
      "address": ""
    }
  }

And a command to set the active instance?

@jbrea
Copy link
Author

jbrea commented Jan 2, 2025

Yes, this sounds like a great idea! Maybe workspaces instead of instances to be fully coherent with obsidian.nvim, and include the API key? i.e.

  workspaces = {
    {
      "name": "",
      "address": ""
      "rest_api_key": ""
    },
    {
      "name": "",
      "address": ""
      "rest_api_key": ""
    }
  }

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

No branches or pull requests

2 participants