Maurice 44eff7177e feat(client): open TREK on the active trip when asked to ...

Settings -> General -> Startup: start on the dashboard (unchanged default)
or straight in the active trip, on a tab of your choice. Three clicks and
three loads less for someone entering expenses while actually travelling,
which is where the request came from.

The redirect sits on '/' because that is what a shortcut, a bookmark and
the installed PWA all launch (manifest start_url). /dashboard keeps
working as itself - redirecting there too would leave no way back to it.

The preference is mirrored into localStorage, the way the language and
the theme snapshot already are, so the first paint can decide without
waiting on GET /api/settings. That keeps the default launch exactly as
fast as before: only someone who asked for the trip pays for the lookup,
and if it fails or they have no trip they get the dashboard. Right after
login the store already holds the real settings, so those win there.

Login stops hardcoding /dashboard as its fallback and hands the decision
to the same place, so there is one answer to "where does TREK open".

2026-08-08 23:01:40 +02:00

..

fileDownload.test.ts

Release 3.1.0 (#1185)

2026-06-16 22:22:45 +02:00

formatters.test.ts

fix(reservations): honour the 24h time setting (#1725)

2026-07-29 15:14:21 +02:00

startDestination.test.ts

feat(client): open TREK on the active trip when asked to

2026-08-08 23:01:40 +02:00

videoPoster.test.ts

test(pages): cover the page hooks, stores and the api client

2026-07-29 11:55:31 +02:00