Important Note
Popularity of a Feature Request is one of the factors we consider when we decide which new features to implement. Therefore, we strongly recommend you to search the forum with possible keywords.
If your request is very similar to an existing one, like it () and make a meaningful comment, rather than creating a new thread. It also keeps the forum sane! If you find duplicate threads, feel free to send the moderators a message.
Feature requests for the Obsidian Developer API go here
Feature requests for Obsidian Importer go here
Feature requests for Obsidian Web Clipper go here
Feature requests for Obsidian Maps go here
Once you are done reading, please delete the above notes
Use case or problem
I am currently writing an integration of obsidian-headless feat: headless sync by neo451 · Pull Request #790 · obsidian-nvim/obsidian.nvim · GitHub currently, all the subcommands have plain text output, even though they are already pretty structured, so to write script that use these info, like once I run ob sync-create-remote, I get
❯ ob sync-create-remote --name 'hi'
End-to-end encryption password (leave empty for standard encryption):
Creating vault...
Vault created successfully!
Vault ID: <VAULT_ID>
Vault name: hi
Region: Europe
Encryption: managed
so I have to do some string matching on this, which is not ideal
Proposed solution
It would be nice to have
❯ ob sync-create-remote --name 'hi' --json
and get a clean json output that can be easily parsed
Current workaround (optional)
string matching as described above, and pruned to change