mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-18 21:16:47 +00:00
Maurice
f0e4c9a33d
An explicit null on a place's duration_minutes advertised a reset it never performed: the column sat behind COALESCE, so null and absent were the same thing and the day plan kept budgeting the old stay length. It clears now, and 0 still writes 0. update_trip_file and link_trip_file never learned the budget_item_id target the REST routes gained, so a receipt could not be attached to an expense from MCP. Added to both, along with the cross-trip check that goes with it: adding the field without it would have opened the hole the same change closed for REST. The roadtrip preferences PUT dropped the X-Socket-Id it was given, so the tab that saved a setting received its own change back and spent a second store commit and a route recompute on an answer it already had. Its two siblings on the same feature forward it. A shared journey did not carry the three "this journey does not use that field" switches, so the phone card read undefined, decided everything was switched on, and showed mood and weather chips on a journey whose owner had turned them off. An entry's country flag followed the pin when the entry was edited and not when the trip sync moved the place underneath it, so a stop dragged across a border kept the old flag with nothing to ever correct it. Also: dawarich.helpers.ts held a raw NUL byte as a hash separator, which made every search tool treat the file as binary and skip it. Same character, written as an escape.