On Wed Nov 9 23:02:18 2022 +0000, Esme Povirk wrote:
That sounds like you're describing the implementation. At a higher level, what is it supposed to do? I need a simple enough answer to keep in my head, so that I can verify that it's correct in isolation, and that it's being used correctly.
![3955d6b06868548df116124fdc4ce119255524a1-1](/uploads/b8b3e4df363352983130fe522b255632/3955d6b06868548df116124fdc4ce119255524a1-1.jpeg)
For a visual example. Let's say you start at node 5, and your current view condition is the control view. In the control view, 3 is a sibling of 5. So, to get 5's sibling:
- Navigate upwards. - Confirm that the parent doesn't match the view condition, or else it'd be the parent of node 5 and therefore node 5 would have no more siblings. - If it doesn't match the view condition, get it's sibling and return.