Provide an option that allows the rendering of connection lines representing the hierarchy of parent and child nodes.

The functionality we would love to see is the ctrl+click/shift+click functionality for selecting checkboxes more efficiently. The reason for this is in several use cases, our users will have 100+ items to select under a single parent. In many cases, they will need to select about 1/2 of them. So the only option at that point will be to select all 50 or select the entire parent and 50.

Having a mechanism to more efficiently select/ (such as shift+click) would be ideal.

It would be useful if the TreeView can support the Angular Routing feature, for example allowing to set a RouterLink directive for each item of the tree.

We are trying to scroll treeview to item that should be selected after page load (and tree automatic expand). Provide a built-in way to scroll to a programmatically selected item.

Please provide an optional callback function when rebindChildren has finished and the tree is stable again.

Thanks

Provide an option to specify the drag target.

Currently, we can click anywhere on the item and drag it. But there are scenarios where the items should be draggable only when clicking an icon.

Hi,

Having a scrollTo method, similar to the one in the Grid component(API), would be a very useful feature for the TreeView component.

I'm aware of the solution described https://www.telerik.com/forums/is-there-a-way-to-set-a-treeview-busy-like-grid's-loading but it would be nice to have a way to control build-in loading indicator instead of implementing a custom one.

 

In a scenario when the data is stored in the state and fetch children immediately returns empty observable and then when data is available and emitted to the source observable you can't see the loading indicator.

An example:

https://stackblitz.com/edit/angular-wtvg2h?file=app/categories.service.ts

Click to expand a category, the "expand" icon is changed to "expanded" but no data is available yet. Two seconds later when data arrives it looks fine, but it would be really good to improve users experience and show a build-in loading indicator while data is not yet available

Hi,

Please provide an option that allows exposing the TreeView nodes' indexes. Such a feature will be especially helpful when rearranging the TreeView nodes by dragging.

Thank you

Hello,

 

We would like to be able to customize icons used in kendo-treeview (ex: arrows to access child elements).

This is required to match the rest of our style guide where we only use fontawesome icons.

Having still some kendo UI icons feel a bit weird at the moment.

 

Thanks!


Regards

Hi,

Please provide a property that can be used to associate the node pageSize with a specific property of the data items.

thanks

Currently, the TreeView has a focus event for the component. However, when the focused node is changed programmatically using the focus method,  there is no event. Can we have a built-in event for this?

Request related to - https://github.com/telerik/kendo-angular/issues/3452

Currently, the default filtering mode, known as "lenient", halts its search as soon as a match is identified, showcasing all child elements of that match irrespective of their correspondence with the filter term. However, due to this design, using "lenient" mode while simultaneously auto-expanding child elements matching the filter term is not feasible.

In the "lenient" mode, the algorithm terminates its comparison upon encountering a match. Consequently, utilizing "lenient" mode along with automatic expansion of potential child matches requires switching to the "strict" filtering mode. This compels the algorithm to perform comprehensive comparisons throughout the entire tree, ensuring explicit identification and expansion of all matches.

https://stackblitz.com/edit/angular-5oxrjd-m3qsi6?file=app%2Fapp.component.ts

An enhancement can be introduced by incorporating a setting that drives the algorithm to perform exhaustive comparisons even within "lenient" mode, introducing the capability to expand matches while maintaining the current operational design.

Since the itemLookup as the selectedKeys works with index and is not able to search the tree by a key value, which in my opinion is really a must-have feature for the tree.

It would be by far easier if we could have a method findParentsByKey and findParentItemsByKey and define a key and values and get the full results.

Like for example

findParentsByKey(id,  123)  - this could return an array of objects of the key/values of the parents of the node with id: 123.

findParentItemsByKey(id,  123) - return only the parent nodes (only those with children), an array of objects with the key/values of each parent item.