Nice. Just noting that using NavigationPath() can give you a little more flexibility in defining destinations without requiring a single enumeration and destination handler that must know and understand every dependent child path.