Cal: Apply buffers of existing bookings too, so buffer protection is not order dependent
Calendly blocks the buffer around every Calendly meeting, so a 30 minute meeting with 15 minute buffers reserves 60 minutes (https://calendly.com/help/how-to-use-buffers). In lib/calendar.ts the buffer is only added to the candidate slot (applyBuffer in slotsForDay, pickFreeHost and HOST_FREE_SQL), while existing bookings are compared with their raw starts_at/ends_at. With bufferAfter=15, booking 8:30 to 9:00 first and then 9:00 to 9:30 is allowed with zero gap, but the reverse order is blocked. Hosts who rely on buffers for travel or prep get back-to-back meetings depending on who booked first. First scope: store the buffered range (or the buffer minutes) on each booking and expand existing bookings by their own buffers in listBusyRanges and HOST_FREE_SQL, plus a unit test for both orders. Priority: high. Effort: S. Compared with Calendly.
Comentários 0
Ainda sem comentários.
Entre para comentar