Fix farthest booking calculation being cut by 1d#1724
Conversation
davinotdavid
left a comment
There was a problem hiding this comment.
Hmm, I don't see this problem happening in the main branch? Here's what I did to try to reproduce:
I've changed my Availability to 7 days and I have tried with all day events and regular events and it still shows blocked (correct) in the booking page 🤔
Well that's interesting. The 7th day shows correctly blocked events? What happens if you switch to 14 and look at the last day?
Good to know that you could reproduce that Rob. So it seems to only happen to some, there might be another variable at play here I'm not aware of 😅 |
davinotdavid
left a comment
There was a problem hiding this comment.
Interesting. I was able to reproduce this only with the 14-day availability block somehow. There might be something move to this but I'd say we can give this a try since it is an improvement over the previous code. Thanks!


What changed?
This change fixes a bug where the last day of an availability time window wasn't considered for remote event retrieval.
How to test
Why?
Prevention of bookings at potentially already blocked times.
Limitations and Notes
It would be good to have tests for those event edge cases.
Applicable Issues
Closes #1719
Screenshots
None