You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say I have an event that goes from 02/08/2024 00:00:00 until 04/08/2024 00:00:00. It is supposed to show as a three-days long event. Problem is that the end date shows as 03/08/2024. I have to set at least one minute at the end (04/08/2024 00:01:00) so it renders correctly. The date conversion is correct, it's translated correctly and everything else seems to work as expected. Please see the sandbox with the problem. I copy-pasted my actual running code, just stripped the typescript and commented out next navigation.
Expected Behavior
The event should render on the correct days span regardless of the end time (hours, minutes, seconds).
Actual Behavior
It doesnt show the correct days span if the end time is something between 00:00:00 and 00:00:59.
Check that this is really a bug
Reproduction link
https://codesandbox.io/p/sandbox/nice-https-lyxs9d?file=%2Fsrc%2FApp.js
Bug description
Let's say I have an event that goes from 02/08/2024 00:00:00 until 04/08/2024 00:00:00. It is supposed to show as a three-days long event. Problem is that the end date shows as 03/08/2024. I have to set at least one minute at the end (04/08/2024 00:01:00) so it renders correctly. The date conversion is correct, it's translated correctly and everything else seems to work as expected. Please see the sandbox with the problem. I copy-pasted my actual running code, just stripped the typescript and commented out next navigation.
Expected Behavior
The event should render on the correct days span regardless of the end time (hours, minutes, seconds).
Actual Behavior
It doesnt show the correct days span if the end time is something between 00:00:00 and 00:00:59.
react-big-calendar version
1.13.1
React version
18.3.1
Platform/Target and Browser Versions
Windows Chrome 127.0.6533.89
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: