Skip to content

handle removed children category container #38

Description

@mariusheine

Imagine you have a column with dynamic amount of columns.
When you decrease the column count the children container for the last column gets removed.
If that container had elements inside then these elements stay in the schema node as invisble artifacts.

If you increase the column count again these artifacts are again visible.

Proposal for handling:

  • delete the nodes of the deleted children container
  • move the nodes of the deleted children container to another still existing container

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions