mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-21 11:36:05 +00:00
8ab7547edf
The calendar feed and the .ics export wrote a restaurant booking linked to a plan stop twice, and the booking's copy without a time zone: - The zone of a booking came only from its own place. A booking whose place is its linked stop (reservations.assignment_id) had none, so its DTSTART and DTEND went out as floating times and calendar apps placed them in the device's zone, an hour early for a London lunch read in Paris. The zone now comes from the booking's place, then its linked stop's place, then the zone all stops of its day or of the trip agree on. Transports keep their endpoint zones and still float when those are unknown, since either end can be in another zone. - The stop and its booking were both emitted (trek-assign-<id> and trek-res-<id>). As for hotels, a stop whose booking yields a timed event on the same day is no longer emitted on its own; the booking event takes over the stop's place as LOCATION, its notes and, when it has none, its end. A booking without a clock, on another day, or still staged leaves the stop as it was, so no event is lost. The VTIMEZONE builder moved unchanged into calendar-timezones.helpers.ts to keep the service under the size cap. Closes #3150