mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-13 07:40:59 +00:00
8e8cff8105
A partial update that left day_id out (a notes-only PUT, an MCP update_reservation or update_transport call) re-derived the day from the stored reservation_time whenever one was set. A time-only value such as "12:00" resolves to no day, so the booking's day_id was written as null and it vanished from its day in the planner. The end_day_id branch did the same when a time-only reservation_end_time was sent. The day is now derived only when the time carries a date that resolves to a trip day; otherwise an omitted day_id or end_day_id keeps the stored value. A dated time still re-pins the day, an explicit day_id null still clears it, and a cleared end time still clears end_day_id. REST and both MCP update tools share updateInTx, so the fix covers all three. Tests: service unit cases (RESV-SVC-044..048), an e2e case per behaviour on PUT /api/trips/:tripId/reservations/:id, and an update_reservation MCP case, all seeded with the ORM factories. Fixes #3025
21 lines
892 B
JSON
21 lines
892 B
JSON
{
|
|
"scripts/db-call-graph.mjs": 1036,
|
|
"scripts/generate-entities.ts": 2259,
|
|
"src/db/repositories/Places.repository.ts": 1437,
|
|
"src/db/repositories/Reservations.repository.ts": 1559,
|
|
"src/db/repositories/Trips.repository.ts": 1121,
|
|
"src/db/repositories/Users.repository.ts": 1445,
|
|
"src/nest/atlas/atlas.service.ts": 1177,
|
|
"src/nest/auth/auth.service.ts": 1143,
|
|
"src/nest/budget/budget.service.ts": 1607,
|
|
"src/nest/collections/collections.service.ts": 1426,
|
|
"src/nest/doc-sync/doc-sync.service.ts": 1060,
|
|
"src/nest/doc-sync/providers/synology-drive.client.ts": 1160,
|
|
"src/nest/journey/journey-domain.service.ts": 1659,
|
|
"src/nest/places/places.service.ts": 1549,
|
|
"src/nest/plugins/plugin-runtime.service.ts": 1460,
|
|
"src/nest/plugins/runtime/plugin-sdk.ts": 1093,
|
|
"src/nest/reservations/reservations.service.ts": 1228,
|
|
"src/nest/vacay/vacay.service.ts": 1409
|
|
}
|