feat: offer rooms on request by Anf code suffix
This commit is contained in:
1 parent
2936d8947a
commit
0b0286787b
11 files changed
+204
-41
No files matched your search
@@ -270,8 +270,9 @@ them a website shows, and how, is the client's rule, not this endpoint's.
|
||||
|
||||
**Which rooms can be booked.** Each room carries `bookable`, the one derived field: `true` exactly when the
|
||||
booking flow offers the room for a new booking. That is status `Frei` with `available` above 0. A room on request
|
||||
(`Anfrage`) is not bookable even with rooms left, because booking it would only produce an inquiry; neither is a
|
||||
room with `available` 0 or `null`. Show a room that is not bookable as sold out and do not count it towards places
|
||||
(`Anfrage`) is not bookable even with rooms left, because booking it would only produce an inquiry, unless its
|
||||
`code` ends in `Anf` (case-sensitive, e.g. `6erSDAnf`): the office sells such a room on request on purpose, it is
|
||||
`bookable`, and booking it makes the whole booking an inquiry. No room with `available` 0 or `null` is bookable. Show a room that is not bookable as sold out and do not count it towards places
|
||||
or the "ab" price. Read `bookable` rather than deriving it from `status` and `available`, so a change to the rule
|
||||
reaches you without a client change.
|
||||
|
||||
|
||||
+7
-5
@@ -80,11 +80,13 @@ Trip rules (`App\Chatbot\TripCatalog`):
|
||||
shown under its TYPO3 title, and under BusPro's name only when TYPO3 has no hotel for its code.
|
||||
`query` searches both. Trips have no name in BusPro's export, only a code; their names are TYPO3's.
|
||||
- A room is listed unless its status is `Buchungsstop`. The baby row (room code `Baby`) is not a room.
|
||||
A listed room is bookable when the booking flow offers it (`Frei` with rooms left, the export's `bookable`);
|
||||
any other room, including one on request (`Anfrage`), is sold out, as the website shows it. Dates with
|
||||
only sold-out rooms stay in `search_trips`, marked `ausgebucht`. `available` counts rooms, so the places
|
||||
of a date at a hotel are `Σ available × maxPax` over its bookable rooms, and the "ab" price is the
|
||||
cheapest bookable room's. The tools never output room counts, only `frei` or `ausgebucht`.
|
||||
A listed room is bookable when the booking flow offers it (the export's `bookable`): `Frei` with rooms
|
||||
left is `frei`; `Anfrage` with rooms left and a room code ending in `Anf` (sold on request on purpose,
|
||||
booking it produces an inquiry) is `auf Anfrage`. Any other room, including any other one on request, is
|
||||
sold out, as the website shows it. A date at a hotel is as available as its best room; dates with only
|
||||
sold-out rooms stay in `search_trips`, marked `ausgebucht`. `available` counts rooms, so the places of a
|
||||
date at a hotel are `Σ available × maxPax` over its bookable rooms, and the "ab" price is the cheapest
|
||||
bookable room's. The tools never output room counts, only `frei`, `auf Anfrage` or `ausgebucht`.
|
||||
- `search_trips` only offers products that TYPO3 lists in its own website search (`searchable`) and does
|
||||
not mark as unbookable. Closed group trips and staff trainings are `searchable: false`. `get_trip` still
|
||||
answers when someone names their code.
|
||||
|
||||
Reference in new issue
Block a user