When populating a Tree or a TreeGrid, I want to be able to construct the data without accessing TreeData for simplicity

[hesara]

Provide API on Tree/TreeGrid level for easily constructing in-memory content.

Based on feedback from @mstahv .

[Legioth]

Constructing data is already doable through setItems(Collection<T> rootItems, ValueProvider<T, Collection<T>> childItemProvider).

Was this ticket based on the discussion about being able to also modify the data directly through e.g. TreeGrid instead of doing getTreeData()?

[hesara]

Yes, I believe the idea was to be able to construct or manipulate data through an API on the component itself. This approach has some issues as the API cannot apply to all instances with an arbitrary DataProvider, so I guess the setItems() mentioned by Leif (already implemented) is the best we can do right now.

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!