Releases: lukasbach/react-complex-tree
Releases · lukasbach/react-complex-tree
Release list
2.6.2
2.6.1
Bug Fixes and Improvements
- switch JSX.Element to React.ReactElement to support React 19 and 18 (#437)
2.6.0
Bug Fixes and Improvements
- If a tree environment renders without an item defined as focused in its
viewStateparameter, it will invoke theonFocusItem
prop with the first item in the tree during its render. In the past, this was implicitly and silently set in theviewStateprop,
now this assignment is triggered explicitly with the handler call (#363) - Fixed a bug where an additional invalid drop target would be available at the bottom-most location when dragging via keyboard interactions (#363)
2.5.0
Breaking Changes
- Changed default keybinding of
startProgrammaticDndtoControl + Shift + D(fromControl + D) since the old
binding conflicted with the default browser behavior of bookmarking the current page. You can customize the
value with thekeyboardBindingsprop.
Bug Fixes and Improvements
- Improved keyboard-controlled drag and drop behavior to not show redundant drop target directly below opened folder item (#363)
- Fixed an issue where the
toggleSelectItem(Ctrl + Space) hotkey could not be rebounded or disabled (#363)
Other Changes
- Added some documentation on the data structure required by a StaticDataProvider.
2.4.6
2.4.5
2.4.4
Features
- Introduce
disableArrowKeysprop on tree environment to disable arrow-related hotkeys (#363)
2.4.3
Features
- RTL mode can be used on default renderers, see docs for details (#369)
- Redirect focus to first item if focused item was dragged to hidden location (#362)
Bug Fixes and Improvements
2.4.2
Bug Fixes and Improvements
- Fixed an issue where sometimes the uncontrolled tree environment would throw undefined-access errors (#355)
2.4.1
Bug Fixes and Improvements
- Fixed a bug where items where sometimes inserted with inverted order. (#353)
- The
onDropshould be a bit faster in general, since some redundant calls todataProvider.onChangeItemChildrenhave been removed. In the past, this was called twice per item, once for moving the item out of its old folder, and once for moving it into the target folder. Now, all insertion calls into the target folder are batched into onedataProvider.onChangeItemChildrencall for all dragged items.
- The