Description of the limitation and why it is relevant to address
As a end user I want to be able to collapse a dynamic array entry so that I have a clearer overview in the app parametrization.
I think this is relevant for the VIKTOR platform because: I really appreciate the dynamic array feature as it provides incredible flexibility in our designs and parametrization. It helps us avoid nested entities and maintain a simple, ‘flat’ interface. My experience is that users lose track of their position when we use nested entities to much. The main issue with dynamic arrays is that they can become quite large over time, leading to lengthy parametrizations, excessive scrolling, and a loss of overview. It would be highly beneficial if these cards could be made foldable/collapsible.
Submitter proposed design (optional)
Fold/unfold dynamic array card.
Current workarounds
I could introduce a BooleanField to control the visibility of the fields. However, I’m concerned that this might lead to unexpected behavior. It also pollutes the parametrization with fields that are actually not really a parameter but just a view option.