Inherit grouping function beyond using view to combind two Inputs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
The issue names no files, tests, or entry points; begin by locating the input and grouping implementation and its existing tests. Clarify which of the three proposed designs is wanted, then define the expected combined value and verify single- and multi-select behavior.
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?
If you want to get to get Color-Number
The only way to achieve that is to:
Make two inputs that record into two different properties.
Then create a view that combines them.
That creates two unnecessary property and unnecessary duplicates stored information.
Describe the Feature you'd like
What i propose is either of three:
Simple option is doubleSelect and doubleMultiSelect types
that has two rows. (It is not exactly clear how multi one should work, and it is probably more logical, that the only difference is that it outputs a list, meaning multiple f them can point to the same property)
OR
Additional value for Option variable, setting it into a separate row.
(such as, for simple select, of "red (option 0)" "- three(option 1)" output will be "red - three" )
OR
A separate group syntax. To merge two or more inputs into one.
Alternatives
No response
Additional Context
No response
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·