Back links are inconsistent and often don't return to the previous screen #308

New issue

Closed

opened 2026-06-27 00:31:40 +00:00 by james · 0 comments

james commented

2026-06-27 00:31:40 +00:00

Owner

The "back" affordances across the universal client (apps/client) are inconsistent: some go back in history, others navigate to a hardcoded parent route, so in many cases "back" does not return to the screen you came from.

Goal

Audit every back affordance (back buttons/links, ChevronLeft/ArrowLeft icons, header back, router.back() / router.replace() / <Link>-to-parent, navigation.goBack()) and make them behave consistently: go back to the actual previous location when there is history, with a sensible fallback (e.g. a parent route) when there isn't — for cases where a screen was reached via deep link or cold start and there's nothing to pop.

Acceptance

One consistent back pattern used everywhere (ideally a small shared helper, e.g. goBackOr(fallback) that uses router.canGoBack() ? router.back() : router.replace(fallback)).
No back affordance hardcodes a destination that ignores history.
Web + native both behave: back returns to the prior screen.
typecheck + lint pass.

The "back" affordances across the universal client (`apps/client`) are inconsistent: some go back in history, others navigate to a hardcoded parent route, so in many cases "back" does **not** return to the screen you came from. ## Goal Audit every back affordance (back buttons/links, `ChevronLeft`/`ArrowLeft` icons, header back, `router.back()` / `router.replace()` / `<Link>`-to-parent, `navigation.goBack()`) and make them behave consistently: **go back to the actual previous location** when there is history, with a sensible fallback (e.g. a parent route) when there isn't — for cases where a screen was reached via deep link or cold start and there's nothing to pop. ## Acceptance - One consistent back pattern used everywhere (ideally a small shared helper, e.g. `goBackOr(fallback)` that uses `router.canGoBack() ? router.back() : router.replace(fallback)`). - No back affordance hardcodes a destination that ignores history. - Web + native both behave: back returns to the prior screen. - typecheck + lint pass.

james referenced this issue

2026-06-27 00:38:04 +00:00

Add pull-to-refresh to each page #309

james referenced this issue from a commit

2026-06-27 00:38:55 +00:00

fix(client): consistent back navigation via goBackOr history-or-parent helper

james referenced this issue from a pull request that will close it,

2026-06-27 00:39:07 +00:00

fix(client): consistent back navigation via goBackOr history-or-parent helper #310

james closed this issue

2026-06-27 01:26:34 +00:00