More
Known limitations
What the first release does not do yet - native drags out of the page, horizontal scrolling, other frameworks - and what stays yours by design.
The first release covers a tree view's behaviour end to end, but not everything a tree can do. Here is what it leaves out, on purpose or for a later release.
Not in this release
- Vertical virtualization only. A virtualized tree (Virtualization)
windows its rows, not its columns: a tree scrolls on one axis. Its rows are flat siblings, so it
renders no
Tree.Group, and a server render of it holds no rows until it is on screen unless you give the virtualizer aninitialViewportSize. - No native outbound drag. Files, links and text dropped on a tree are taken (Foreign content), and rows dropped outside every tree reach your own targets (Dropping outside), but a row cannot be dragged to the desktop or into another window or application. A tree's drag uses Pointer Events (one path for mouse, touch, pen and the keyboard), which never leave the page; a native HTML5 drag out of the tree would be a second mechanism, kept out until the maintainer decides on it. For the same reason trees in two documents (an iframe, a popup window) never share a drag.
- No built-in app policy. Undo and redo, persistence, translations and announcement text are yours: the examples show each one as code to copy.
- React, Vue and Angular. Another framework needs an adapter of its own, over the same core
(
@fragiola/tree).
Known gaps
- The cascade does not skip disabled items. In
cascademode, unchecking a parent unchecks every descendant, a disabled one too, so an action locked as granted is unchecked with its resource. The permissions admin works around it: its check control and Space check only the actions that are not locked (Space through the root'skeyMap), and a middleware refuses any check that would uncheck a locked one. - A controlled
checkedItemIdscan lose checks. When the list a root is given drops a parent the cascade had checked, the root unchecks it, and with it children the list still wants, which it does not check again. Until it is fixed, set checks through commands and let the root report them (the permissions admin presets and Discard do).
Found something else? Open an issue.