Maurice e7851e79ff fix(client): honour the start page on a device that never mirrored it ...

The mirror answered "dashboard" for a browser that had simply never been
told, and RootRedirect took that as the user's choice - so the setting was
ignored on every device except the one that set it, and on that one too
after a logout cleared the mirror. The setting itself was stored correctly
the whole time, which is what made it look like nothing happened.

readStartDestination now says "unknown" rather than guessing, and a device
in that state waits for the real settings instead. That costs one wait,
once per device; afterwards the mirror answers and the launch is as fast
as before. Bounded by a timeout, because loadSettings deliberately leaves
isLoaded false on a failed request so it can retry - without the floor, a
launch with no backend would sit on the spinner forever.

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

..

environment

v3.4.0 (#1540)

2026-07-18 22:13:52 +02:00

helpers

chore(client): move zustand to 5.0.14 (#1825)

2026-08-07 16:34:18 +02:00

integration

feat(dayplan): choose the travel mode per segment (#1281) (#1651)

2026-07-21 23:36:53 +02:00

unit

fix(client): honour the start page on a device that never mirrored it

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

setup.ts

test: give async assertions a realistic budget on CI

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