Bills of materials, account charts and organisation units are hierarchies that users expect to see as indented rows they can fold. This release gives the data grid that shape, and makes the standalone tree share its model.
The tree grid
- Configured, and checked A hierarchy is configured on the grid from a parent and a branch column; misconfiguration throws rather than renders nothing. The branch flag accepts booleans or zero and one.
- Collapse depth The number of initially collapsed levels is configurable, and column grouping can be simulated as a tree.
- Rows dragged Rows move to a position, and the event carries the full list of dragged rows. Row selectors, highlight icons and error cells work on tree rows.
- Per-column rendering through a slot named after the column.
One model
- Grid and tree agree The tree component builds its nodes from the same hierarchy strategy, so a grid and a tree over the same cursor never disagree. Empty folders render, and a hierarchy update rebuilds at runtime.
Tree grids sort on the client, always. That is the one rule a hierarchy imposes.