Completed
Last Updated: 05 Sep 2023 13:43 by ADMIN
Release [R3 2023] PI 2

Describe the bug

The event parameter available in the event handler of the TreeViewCheckChangeEvent has an incorrect type of TreeViewExpandChangeEvent while it should be TreeViewCheckChangeEvent.

Screenshots
image

Unplanned
Last Updated: 19 Jun 2023 15:10 by Matt
Created by: Matt
Comments: 0
Category: TreeView
Type: Feature Request
1

The TreeView Wrapper component provides the autoScroll property that allows the out-of-the-box scrolling of component items when performing drag-and-drop operations.

Please provide the autoScroll property inside the Native TreeView component.

Unplanned
Last Updated: 12 Aug 2022 06:53 by Robert
Created by: Robert
Comments: 0
Category: TreeView
Type: Feature Request
0

The current implementation of the Native TreeView doesn't allow you to customize the expand/collapse arrows of the component. 

Can you please provide a property that allows the definition of a custom class for a given TreeView group? Being able to define such a class, using CSS we can easily control the look of the different elements of each TreeView group.

Completed
Last Updated: 20 Sep 2022 11:13 by ADMIN
Release R1 2023 - Increment 1 (26.10.2022)

Describe the bug

When we have a multi-level nesting in the data loaded in the Native TreeView the parent nodes that are below level0 are not displayed correctly when set as expanded.

Sample TreeView structure
|-Level0
-|-Level1
--|-Level2
---|-Level3

  • The issue is replicable when the "animate" prop of the component is set to "true". If "animate" is set to "false", the TreeView is displaying all its nodes as expected.
  • The issue is replicable when the processTreeViewItems method is used. If the TreeView is directly bound to an array, the component is working correctly. See this example.

To Reproduce
Steps to reproduce the behavior:

  1. Open this StackBlitz project
  2. See nodes "Item1.2" and "Item2.3"

Expected behavior
The "Item1.2" and "Item2.3" nodes should be expanded and their child nodes should be displayed by default as in this example.

Screenshots
image