Multi-day event's end date is not inclusive

This is the design behaviour of FullCalendar.

See below for more information.

https://fullcalendar.io/docs/nextDayThreshold

nextDayThreshold may solve the problem if the events are not allDay. However, my events are allDay and in that case the documentation says that nextDayThreshold is ignored.

Based on another Fullcalendar issue, if a Fullcalendar user wants to make the end date inclusive for allDay events, the recommended solution is to adjust the end date before passing to Fullcalendar.

Would it be worthwhile to provide an option within the Fullcalendar Block module to make the end date inclusive? If not, perhaps just document how to do this? (I'd be willing to write the documentation.)

I would vote for a document or amending an existing document to mention how to make the Fullcalendar work in this case.

jlstrecker → changed the visibility of the branch 3477144-multi-day-events-end to hidden.

I created a merge request with documentation for the case of allDay events.

I looked at whether it would be helpful to add something about events that are not allDay, but it didn't seem like there was anything worth adding. I tested some events spanning multiple days to see if there was anything potentially surprising. The only case where it made a difference if the end date was exclusive or inclusive was if you had an event that ended at midnight.

Thanks @jlstrecker for raising this issue.

This issue (question) has been raised to Fullcalendar.js since 2015, almost 10 yers ago.

https://github.com/fullcalendar/fullcalendar/issues/2985

I understand the confusion and agree with that if we don't want to change the designed behaviour by Fullcalendar.js, we need to mention it in the document.

Speaking of document, I would suggest mentioning it in the user guide document → .

I apologise that I didn't reply it clearly. The reason why I don't think we should put this inside of the README.md file, is that the targeted audience of that file is a developer, since that file is hosted in Gitlab. Given that, I suggest putting it into the user guide document → .

I think everyone should have the edit access to the Drupal document.