Behaviour change in isVisible

[TiaxDev]

Hi,

I've been using an older version of BasicPrimitives (5.9.2).
I've recently tried out the latest version (6.5.1) and the migration went smootly (i just had to replace and refactor my templates due to the 6.0.0 non-backward compatible API changes) until i noticed a small change in the behaviour of the isVisibile property (i'm using OrgItemConfig).

With BasicPrimitives 5.9.2, i was able to completely hide some items with that property (connectors were also hidden).

After the update, the behaviour seems to be changed. When i trigger the isVisible property on an item, the template is hidden correctly, but its connectors with the parent seems to remain visible.

According to the API reference, the current behaviour of isVisible is correct, due to the fact that my items are actually related to visible parents:

If false, it makes the item invisible in the layout. If the item has no visible parents, its connections are hidden as well. From the navigation perspective, children of hidden nodes become children of their parents.

Despite this, the behaviour change is breaking some of my logics and i wasn't able to achieve such layout without completely removing the item from the structure.

Is there a way to achieve the previous behaviour, hiding the item and its connectors, without actually removing the item itself from the structure?

Thanks

[BasicPrimitives]

What we need to do is to test your data set for leaves having isVisible flag set to false and remove them from dataset. Yes, it is not a big deal, but if you have 5000 nodes and only 500 of them are visible, our control will be slow for no reason. We will scab 5000 nodes and remove 4500 nodes having isVisible set to false, on every update. Yes, we can do it, but as a result we will make control slower for everybody, because it will perform unnecessary transformation of every update. This issue has no functional value and makes View to step into View Model responsibilities.