You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is possible to have a dynamic list with no visual elements (expression). This means we can add a bunch of empty rows to a dynamic list. While this affects the state normally, we would rather simply not allow this.
Further investigations: The issue is more complex as it is also needs to consider cases where hide if causes an empty list element. I think we should accept empty items as part of the debugging process, not caring about whether it stems from expressions, hide if, or any other non-visual element. But instead, we should have a more parseable visually empty state instead of what we see below:
This is a bit of a pain to handle right now, we should wait on the render refactors for this.
Steps to Reproduce
Add a dynamic list
Add an expression component inside
Items are empty but not very understandable
Expected Behavior
Items should have some information of the type "no visual elements available in item"
The text was updated successfully, but these errors were encountered:
Following some more considerations, this should not be tackled until we decouple rendering from form state management. I believe we should have a type of "no visual elements" node rendered instead of strictly treating the whole dynamic list as empty (since this is all dynamic relative to hide-if conditions).
So overall, on hold until refactors.
Skaiir
changed the title
Treat a dynamic list with no visual elements as empty
Render an informative div inside dynamic list items with no children
Sep 10, 2024
Describe the Bug
Currently it is possible to have a dynamic list with no visual elements (expression). This means we can add a bunch of empty rows to a dynamic list. While this affects the state normally, we would rather simply not allow this.
Further investigations: The issue is more complex as it is also needs to consider cases where hide if causes an empty list element. I think we should accept empty items as part of the debugging process, not caring about whether it stems from expressions, hide if, or any other non-visual element. But instead, we should have a more parseable visually empty state instead of what we see below:
This is a bit of a pain to handle right now, we should wait on the render refactors for this.
Steps to Reproduce
Expected Behavior
The text was updated successfully, but these errors were encountered: