mProjectsCode / mProjectsCode/obsidian-meta-bind-plugin

"Option Tags" Input Field Arguments for use with suggester, list, and select Input Fields.

Open
#423 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request priority-high
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'm frustrated when I want to type a tag in to a suggester, list, or select field, and I receive no auto completion hints for the tags that are available.

Describe the Feature you'd like

I would like an optionTags Input Field Argument that can be mixed in just like the existing option and optionQuery arguments.

When used, it should include existing tags in the available values.

A string argument to optionTags should limit the returned tags to those nested under the tag named in the argument.
For example, optionTags(#include/me) should cause options to appear for tags #include/me/A and #include/me/B, but not #other/tag.

Alternatives

I tried using the optionQuery argument, but it is limited to Dataview sources. While a tag can be a source of querying for pages, a list of the tags themselves cannot be retrieved this way.

Additional Context

The suggester UI is already well suited for this feature.

For the list, and inlineList types, I wonder if it would be possible to reuse Obsidian's built in feature that hints values for the tags property that appears at the top of the file in preview view mode.

For select types, I think it should be available, unlike the optionQuery argument that is not available. Perhaps an additional number argument to optionTags to limit the number of results would be worthwhile.

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

Start by tracing how input field arguments handle the existing option and optionQuery arguments, then inspect the suggester, list, inlineList, and select entry points. Done means existing tags can be offered as values, with an optional parent-tag filter such as #include/me applying consistently to the requested field types.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.