- Select one or more Properties (MV codes). These map to propertyId internally. (will map with property names in future)
- Add one or more Event date(s) We will add more features, such as accepting date ranges or providing an easier way to select event dates, to simplify the process when handling 100+ events..
- Set Min LOS (nights).
- Add
- Show Components → validated against
showComponents using start and end as eventDate.
- Inclusion Components → validated against
inclusionComponents using minLOS ranges per event (we exclude ranges whose end equals the event date).
- We will integrate the RBS API and make sequential calls to the component API once Dileep agrees 😅 to move it forward. For now, we will paste the response in the JSON section and click Submit to build the table.
How the Table is Constructed
For each event date and minLOS, we generate possible stay ranges.
- For Show Components, we only match the exact eventDate – eventDate.
- For Inclusion Components, we match each generated stay range, except those ending exactly on the event date.
Example:
- Event date =
2025-08-30
- Min LOS =
2
- Property =
MV938
- Component code =
S
- Inclusion code =
I
The system will construct a table like this:
| stayDates |
property |
code |
price |
| 30 Aug – 30 Aug |
MV938 |
S |
(from showComponents) |
| 29 Aug – 31 Aug |
MV938 |
I (incl) |
(from inclusionComponents) |
| 30 Aug – 01 Sep |
MV938 |
I (incl) |
(from inclusionComponents) |
| 31 Aug – 02 Sep |
MV938 |
X |
0 (row shown in red if not found) |
⚠️ If a component or inclusion is not found in the JSON for a given stay range,
that row will still appear with price = 0 and be highlighted in light red.