mProjectsCode / mProjectsCode/obsidian-media-db-plugin
Option to group YAML under a single key
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 491
- Forks
- 52
- Avg merge
- 2h 17m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Sometimes the YAML key names created by the plugin are duplicates of YAML keys that I'd like to use in the document for something else, e.g. id:.
Describe the solution you'd like
It would be convenient to have an option to group the YAML under a single customisable key, by default mediaDB: for example. This way any YAML keys that the plugin outputs can't be duplicates of any that I've created at the root level of my front matter. I'd hope such an option would also take effect when copying to clipboard (#107).
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating where the plugin generates YAML front matter and where it copies generated metadata to the clipboard; issue #107 is the related clipboard context. Done means the generated YAML can be placed under a configurable root key, defaulting to mediaDB, in both document imports and clipboard output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- content
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100