matuzalemsteles
commented
2 years ago I'm adding some thoughts as I'm working on this. One of the big downsides of implementing virtualization for tree based structure is that we need to convert the data to list structure this has some issues I see:
- Computing the traversal of the data on render, this might not be too bad because it can be optimized and not need to traverse the entire tree.
- It won't be accessible, as all nodes are rendered in a single list instead of nested and the group semantics doesn't fit here and this is very bad especially for DropDown which has to be accessible.
It won't be accessible, as all nodes are rendered in a single list instead of nested and the group semantics doesn't fit here and this is very bad especially for DropDown which has to be accessible.
This is an extension of issue #5009, to better understand the context I recommend reading the comments in PR #5013. Following the implementation of the Collection pattern, to finish this first step we need to implement the Tree virtualization functionality for the Collection, this case would be more exclusive for the TreeView but it is quite likely that we can also use it for more complex cases with DropDown that has some nested items.
As a goal this issue should implement the functionality of virtualization in Tree and asynchronous paged loading of data for the
useResourcehook.