Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of List type for fields #313

Open
TheNoteTaker opened this issue Aug 20, 2024 · 2 comments
Open

Addition of List type for fields #313

TheNoteTaker opened this issue Aug 20, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@TheNoteTaker
Copy link

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.

@TheNoteTaker TheNoteTaker added the enhancement New feature or request label Aug 20, 2024
@TheNoteTaker TheNoteTaker changed the title [Feature request] Addition of List type for fields Aug 20, 2024
@danielo515
Copy link
Owner

danielo515 commented Aug 20, 2024 via email

@TheNoteTaker
Copy link
Author

TheNoteTaker commented Aug 25, 2024

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants