mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-13 07:40:59 +00:00
2f3a0219cd
A booking file without a booking ended the answer on the error "No booking found in this file." with no action, and the user was left to type. Now the server answers every booking file itself, without a model: one line that names the file and what TREK found in it, or that it found nothing, why, and asks what to do with the file. Under it come up to three chips, picked from what the user may do on the trip and what the file allows: keep it in Files, make a booking from its text, attach it to a booking or an expense, ask what is in it, or keep it with the booking just found. A chip sends its words as an ordinary chat message. The line and the chips are written in the language of the request from new assistant.attach.* keys in all 27 locales, through a small helper the sports proposals now share. The empty answer finishes as stop; no_bookings_found stays in the contract for the threads older builds wrote. Route files keep their answer as it was.