aiolabs/webapp
9
0
Fork 0
Code Issues 70 Pull requests Projects Releases Packages Wiki Activity Actions

fix(chatelet): let a min-stay range extend forward (reka span guard) #158

Merged
padreug merged 1 commit from fix/chatelet-min-nights-range-spanning into dev 2026-09-21 12:32:09 +00:00
Conversation 0 Commits 1 Files changed 1 +12 -2
1 changed files with 12 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
src/modules/chatelet/components/StayDatePicker.vue
View file

@ -122,7 +122,13 @@ function isDateDisabled(d: DateValue): boolean {
}
if (y === start) return false
if (y > start) {
if (y < addDays(start, props.minNights)) return true
// Do NOT disable the days inside the minimum-stay window here: reka-ui
// refuses to complete a range that *spans* a disabled day, so disabling
// start+1 (for a 2-night minimum, etc.) makes every forward check-out
// unreachable — the guest can only click an earlier day, which reka
// swaps in. The minimum stay is enforced in onModel instead (a too-short
// range keeps the check-in and clears the check-out). Occupied nights
// past the next booking still cap the range.
if (boundary.value && y > boundary.value) return true
return false
}
@ -143,8 +149,12 @@ function onModel(v: RekaDateRange | null) {
const ok =
stayIsFree(props.nightSet, ci, co) && nightsBetween(ci, co) >= props.minNights
if (!ok) {
// Defensive: reka let a bad range through — keep the check-in, redo the end.
// A range too short for the minimum stay (or spanning an occupied
// night). Keep the check-in and redo the end. checkOut is already ''
// here, so the props watch won't fire — reset reka's controlled model
// directly, otherwise its highlighted end lingers on the rejected day.
pendingStart.value = ci
model.value = { start: fromYmd(ci), end: undefined }
emit('update:checkIn', ci)
emit('update:checkOut', '')
return