there's nothing limiting the user to add more than one groupOwner in the same group
there's nothing limiting that the first row on a TreeGridRowGroup should be the groupOwner
each TreeGridRow controls it's own visibility (this might not be ideal for virtualization cases, as the visibility of the nodes is dictated by the virtualization library on scroll normally?!)
Changes
TreeGridRowGroup
componentPossible problems with this implementation
groupOwner
in the same groupTreeGridRowGroup
should be thegroupOwner
TreeGridRow
controls it's own visibility (this might not be ideal for virtualization cases, as the visibility of the nodes is dictated by the virtualization library on scroll normally?!)