1ec2d62b1c
Changing a trip's start date positionally re-dates the day rows (keeping their ids), so a dated booking's day_id stayed glued to a now-re-dated day and the booking visually shifted by the offset — until you re-opened and saved it. After a date-range change, non-hotel bookings are now re-anchored to the day matching their absolute reservation_time (the same derivation create/update already use). Bookings whose date falls outside the new range are left untouched; hotels and the relative positional shift of places/notes are unaffected. |
||
|---|---|---|
| .. | ||
| db | ||
| mcp | ||
| middleware | ||
| nest | ||
| services | ||
| systemNotices | ||
| utils | ||
| idempotency-cleanup.test.ts | ||
| scheduler.test.ts | ||
| shared-contract.test.ts | ||