Has anyone figured out NavigationStack/NavigationLink/NavigationPath keeps track of selections?
There's some kind of identity being used, but I can't for the life of me figure it out:
https://gist.github.com/chockenberry/476ef4d8b1bfc73872dda8e0d9d8f49f
And the usual places show lots of developers disabling selections and using other workarounds. The docs don't help much here because the examples are old (NavigationView, StateObject, etc.) and/or use shallow navigation examples.
@chockenberry having myself gone insane on this, the identity is that of the row value. However with cyclic paths like you have, you need a way to differentiate between screens of the same type and value.
One crude way is to introduce a "level" that increments for each screen, though there's likely more elegant ways to achieve the same thing depending on your setup: https://gist.github.com/phillipcaudell/fda686d67bde2f87a9252fbd802fcc3a
@phill Thanks for confirming my suspicions about the row value and how to tweak the objects to get unique hash values. 👍