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
So they reference the same object "taskTree" I imagine someone would need that for comparing two nodes of the same tree in split view or something.... Not sure if its a big issue since you can clone the object and be fine.
The text was updated successfully, but these errors were encountered:
Hi @pawelhandrysik thanks for reporting this. I think you are right, I very much suspect that the issue is caused by the object being the same in both trees. As you said, the immediate workaround is to clone the object and use separate copies, but there might be a use case where the original copy needs to be used in both trees. I'll try and see if I can come up with something.
I have the following structure in my project and the first ng-treetable is not collapsing I can collapse the second component no problem.
As you can see I clicked on the second row but it didn't collapse these two tables are in a single component like so:
So they reference the same object "taskTree" I imagine someone would need that for comparing two nodes of the same tree in split view or something.... Not sure if its a big issue since you can clone the object and be fine.
The text was updated successfully, but these errors were encountered: