danielo515 / obsidian-modal-form

Define forms for filling data that you will be able to open from anywhere you can run JS
https://danielorodriguez.com/obsidian-modal-form/
MIT License
211 stars 18 forks source link

Addition of `List` type for fields #313

Open TheNoteTaker opened 2 months ago

TheNoteTaker commented 2 months ago

Is your feature request related to a problem? Please describe.

No.

Describe the solution you'd like

It's something that is not super high priority, but is a nice quality of life addition. The ability to have a List section which accepts multiple items and then returns an object whose value is an array of strings in post-processing for that key.

danielo515 commented 2 months ago

Sorry, have you tried multi-select ? I think it does exactly what you described

El mar, 20 ago 2024, 3:55, Austin Kaufman @.***> escribió:

Assigned #313 https://github.com/danielo515/obsidian-modal-form/issues/313 to @danielo515 https://github.com/danielo515.

— Reply to this email directly, view it on GitHub https://github.com/danielo515/obsidian-modal-form/issues/313#event-13938160142, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARKJWORORV4RO3NV7DZQMLZSKOY5AVCNFSM6AAAAABMY47AYKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTHEZTQMJWGAYTIMQ . You are receiving this because you were assigned.Message ID: @.*** com>

TheNoteTaker commented 2 months ago

Yes, I didn't realize you could type non-explicitly-defined results. I do have some other actual things I've found having used this plugin a bit more:

  1. When you make a section conditional and then shift it up or down, the condition stays in place and does not shift with it. The new field which was shifted down (or up) will inherit that condition.
    • For example, Foo is in Position 1 and Bar is in Position 2. Bar depends on Foo. When I shift Bar up to Position 1, and Foo naturally goes to Position 2, the conditional will still be at Position 2 and make Foo now depend on Bar.
  2. I have a setup with a category and a subcategory.
    • subcategory depends on category
    • I then have a few fields which depend on subcategory.
    • When I change category, subcategory disappears. The fields which depended on subcategory do not though because that value was set (even if for only a moment). Could you also clear out subcategory value when it's parent changes? This allows for chained conditionals.
  3. The ability to have multiple conditionals would be amazing!
  4. A conditional for regex or (does not contain). For example, I need a field which should show up for all selections of another field except for one. It should not show only when that field is selected.
  5. Changing the value of a field which has child conditions on it will break all of those. If possible, auto-updating any dependencies would be awesome!