You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ve found out, that you provide a reset functionality to operate on openNodes. I am just curious about the data structure of the openNodes. Basically its a "itemA/itemB" etc. Do I have to write my own algorithm, which transform my data, which are being passed to TreeMenu into this form "key/key" etc. I am just wondering if there is a more smooth way to do that :).
BR,
Ales.
The text was updated successfully, but these errors were encountered:
If the default expand/close behaviour meets your requirement, you only need to provide data. But if you have specific requirements, then you have to implement your own logic, this TreeMenu component allows you to manipulate almost everything.
openNodes is used when you want to have full control over every node, and you don't want the default expand/close behaviour AT ALL. You can see the storybook example here. I guess this API is rarely used.
If you only want to set the tree to a specific shape but still allow users to use the tree menu, you can use initialOpenNodes, see example here. This API is more useful I guess.
Hello,
I ve found out, that you provide a reset functionality to operate on openNodes. I am just curious about the data structure of the openNodes. Basically its a "itemA/itemB" etc. Do I have to write my own algorithm, which transform my data, which are being passed to TreeMenu into this form "key/key" etc. I am just wondering if there is a more smooth way to do that :).
BR,
Ales.
The text was updated successfully, but these errors were encountered: