Use case or problem
Scripting for organization use cases can benefit from leveraging metadata from properties. Keeping scripts portable requires introspecting the property taxonomy used by the user: for example, finding the property names via `obsidian properties` and then introspecting the actual values for the properties themselves (not currently supported).
Proposed solution
A command like `obsidian property:list name=` could be added to list all values for a given property in the vault. This would allow scripts to roundtrip for properties, their values, and then use interpolation to craft a good query for `obsidian search`.
Current workaround (optional)
There is a very brittle invocation that can achieve this via `eval` and the Javascript API (example with (example shown with type as the property name):
obsidian eval code="[...new Set(app.vault.getMarkdownFiles().map(f => app.metadataCache.getFileCache(f)?.frontmatter?.type).filter(Boolean).flat())].sort().join(', ')"
It’s also obviously possible to achieve with regexes over the vault contents.