Limit future bookings within a date range is broken;

[brobr]

Limit future bookings within a date range is broken; the opposite is shown. That is: days to show as bookable appear as unavailable and all other irrelevant dates with wrong slots show as available! Did somebody took a negation out of a function?

A summary of the issue. This needs to be a clear detailed-rich summary.

Steps to Reproduce

1. Change scheduling range under event-type/limits
2. Set a date range to span dates with available slots for 10 and 11 March.
3. Cancel all other dates in that time span (because there is no availability).

This kind of action worked a couple of days ago fine; what has happenend?

Actual Results

The opposite is shown: all dates with defined available slots (10 and 11 March) show as unavaliable and all other irrelevant dates show with open timeslots that have never been defined; some default seems to be taking over.

Technical details

• Mozilla Firefox 128.7.0esr (64-bit), Slackware64-15.0+ (current)
• Nodejs-22.14.0

Evidence

Settings for event: slots, dates and overrides

and how it shows up:

[anikdhabal]

@brobr screenshots look fine. Could you pls add a loom or video?

[brobr]

Sorry, cannot make a video.
Steps:

1. Set up 1 hr Event, Save
2. Set Event -> Availability: Slots 7.30 pm - 8.30pm Mon-Fri, Save
3. Event -> Limits: set Limit future bookings, Within a date range Mar 1- Mar 14 2025, Save
4. Edit Event -> Availability: Date overrides: mark all days but 10 and 11 March, Save
5. Test event page in browser or different one (Vivaldi): same result; the inverse/opposite of bookable dates and time slots is shown.

For example: https://cal.com/sdheatteam/1hheatsurvey?month=2025-03