mProjectsCode / mProjectsCode/obsidian-meta-bind-plugin
The ability to limit optionQuery results based on frontmatter data
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
Is your Feature Request Related to a Problem?
No response
Describe the Feature you'd Like
Currently optionQuery() only takes data sources input to limit the alternatives, but I need/want to specify notes more specifically, and would like to be able to restrict the options on frontmatter/property data as well.
Additional Context
No response
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 the TypeScript implementation of optionQuery and trace how its current data-source filtering is represented. Determine how frontmatter or property constraints should be expressed, then verify that matching options are restricted accordingly and existing optionQuery behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- content
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100