Maurice da92581a16 fix(planner): let a route choice survive the map, and keep new items on their day ...

Two things the mobile planner forgot.

The day sheet's route toggle only ever lived in component state, and entering
the map — or tapping a day while in it — forced it back on. Turning the route
off therefore did nothing you could see and had reset itself by the time you
looked again. The choice is now remembered per trip; the map still switches it
on by default, but only while the user has never said otherwise.

Adding a place or a booking from inside a day did not connect it to that day.
The place dropped into the unplanned pool, which on mobile is a different screen
— it looks like the save was lost — and the booking opened with no date at all.
Both entry points now carry the day they were opened from, including a
long-press on the mobile map, where the chip rail names a day at all times. The
desktop map has no such context and passes nothing, so its pool behaviour stands.

While here: the import button on the bookings and transports headers only
appeared when kitinerary was installed, though the server also accepts an import
when the LLM parser is configured (#2007).

Closes #2003
Closes #1998

2026-08-21 13:27:27 +02:00

..

environment

v3.4.0 (#1540)

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

helpers

fix(planner): let a route choice survive the map, and keep new items on their day

2026-08-21 13:27:27 +02:00

integration

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

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

unit

fix(planner): let a route choice survive the map, and keep new items on their day

2026-08-21 13:27:27 +02:00

setup.ts

test: give async assertions a realistic budget on CI

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