mProjectsCode / mProjectsCode/obsidian-meta-bind-plugin

Auto suggester based, value population for suggester style fields

Open
#599 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request waiting on upstream change
Dominant language
TypeScript
Stars
1k
Forks
86
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.