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
Based on some conditions, I have to navigate through "childs" or "details".
I use the partition layout to traverse the tree either by "childs" or "details" by implementing the partition.children callback function.
This works well by I stay with one side of the tree untouched after the traversing.
For my usecase, at the beginning, I need to navigate through the two fields by keeping all the state of the previous navigation. So traversing through all "childs" like it was "children", the same thing for "details"
I didn't find any function in API that can help to achieve this kind of behavior.
Do it possible to perform this double navigation with the partition layout ?
Thanks for your help
The text was updated successfully, but these errors were encountered:
Hello,
At first, I would like to thank you for your great work on this library. It helped me a lot of for all my data visualization usecase.
However, I got a special kind of hierarchical data that I wondering if it is possible to solve it with d3-hierarchy ( partition).
In JSON, I have to 2 fields that can be used as "children", "childs" and "details".
Based on some conditions, I have to navigate through "childs" or "details".
I use the partition layout to traverse the tree either by "childs" or "details" by implementing the partition.children callback function.
This works well by I stay with one side of the tree untouched after the traversing.
For my usecase, at the beginning, I need to navigate through the two fields by keeping all the state of the previous navigation. So traversing through all "childs" like it was "children", the same thing for "details"
I didn't find any function in API that can help to achieve this kind of behavior.
Do it possible to perform this double navigation with the partition layout ?
Thanks for your help
The text was updated successfully, but these errors were encountered: