Missing react component: tree select

[himdel]

TODO: see form dependencies below, describe component, add screenshot, implement

• Simple TreeView Introducing the TreeView component for DDF without React #7356
• Input field with tree select Implemented the TreeViewSelector component for DDF #7410

[himdel]

(the component already exists in angular)

[skateman]

I have a feeling that @brumik has something in his cylinder 😉 IMO we just need to lego together some stuff that already exists. Gonna look into it.

[skateman]

Firstly, I think the catalog item form requires a slightly different approach as it behaves differently than the other screens in the marked issues. There's a text field that opens a modal with a tree where you can select (not check) a tree node. After a selection the modal closes and the value of the node gets copied into the text field. This is what we call tree-selector in angular and if we'd like to keep this behavior, it would need a separate component. This one can easily implemented as a DDF component and incorporated in any form.

The other screens have trees with checkboxes and we operate with the state of the checkboxes, i.e. loading them from the DB and storing it when saving. These are currently converted by @brumik and they aren't really DDF friendly at the moment. They all behave a little differently but after all of them were converted to react, I think it's easier to finish their unification and get rid of the session backed oncheck handling after the conversion happened.

Note that the conversion also incorporates the tree from the catalog entrypoint selection, but so far it doesn't deal with the DDF-ication of the text field that triggers it. Also there's a few other screens where we use the tree-selector implementation:

• embedded methods on automate methods' summary screen (angular)
• target selection when copying stuff in automate
• dialog editor entrypoint selection for dynamic fields (angular)

#6413