diff options
| author | Christian Cleberg <[email protected]> | 2026-07-15 21:56:56 -0500 |
|---|---|---|
| committer | Christian Cleberg <[email protected]> | 2026-07-15 21:56:56 -0500 |
| commit | 575e62f6dab44b0c9836623fe8b7d17a219f8e0f (patch) | |
| tree | ef1740b6841259193e01e868da1dd1df683ae844 /Hutch/Views/Work/WorkView.swift | |
| parent | 22c7a0e45a5cc344e2fa0635431d95c23024ad63 (diff) | |
| download | hutch-575e62f6dab44b0c9836623fe8b7d17a219f8e0f.tar.gz hutch-575e62f6dab44b0c9836623fe8b7d17a219f8e0f.tar.bz2 hutch-575e62f6dab44b0c9836623fe8b7d17a219f8e0f.zip | |
fix: push patchset views directly instead of by route
Tapping a patch failed with "no matching navigationDestination declaration
visible from the location of the link".
MailingListDetailView is presented from four places, but only the More tab and
Lookup declare a MoreRoute destination. Reached from a project, via
ProjectMailingListView, there is no such destination in the surrounding stack,
so a NavigationLink carrying MoreRoute.patchset had nowhere to resolve. The
thread rows beside it already use the closure form for exactly this reason.
Push PatchsetDetailView directly, from the rows and from the version-chain
links inside the detail view, which inherits whatever stack presented it. That
leaves MoreRoute.patchset with no users, so it and its two destinations are
removed rather than left as a route nothing links to.
Neither the compiler nor the tests catch this: it is a runtime SwiftUI
resolution failure.
Diffstat (limited to 'Hutch/Views/Work/WorkView.swift')
0 files changed, 0 insertions, 0 deletions
