Auto suggester based, value population for suggester style fields
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
No files, tests, or entry points are named. Start by tracing the existing Option Query and suggester implementations, then determine how property values are collected and exposed to INPUT fields; done means a property-based suggester is specified, implemented, and covered by tests.
Written by the indexing model from the issue text.
Description
Please fill out these Check-boxes
- I checked for existing similar feature requests
- I have read the docs and checked that the feature I am requesting is not already implemented
- My feature request consists of only one feature
Is your Feature Request related to a Problem or Annoyance?
I use strange properties, it means that rather then 5 or 10 or any set number of values for a property, I have a lot of them and often add new ones.
It is fine inside of the editor, as auto suggest works fine. But with INPUT it is hard to do anything productive, as the only way is to add them by hand.
Describe the Feature you'd like
I would like an ability to populate a suggester, using a property name.
It would work similar to the Option Query, but instead of providing notes, it would use the same stuff editor uses, to provide all existing values for the specified property.
Like propertyOptionQuery(Theme)
where theme is a name of some property.
Alternatives
No response
Additional Context
It makes sense to look into ways to get tags in similar way, but it is a separate feature.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
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.
More from mProjectsCode/obsidian-meta-bind-plugin
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mProjectsCode/obsidian-meta-bind-plugin#669 · 2 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
bug can't reproduce
Difficulty 4/5 3-5 days Newbie friendliness 45/100
mProjectsCode/obsidian-meta-bind-plugin#667 · 9 comments ·
All issues in mProjectsCode/obsidian-meta-bind-plugin
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100