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
I was experiencing with the behaviour and it looks as follows:
when ends_at is less than starts_at, it flips it and looks for conflicting events. In case with 'Dinner' example, it looks for conflicting events from 0:00 till 18:00 and finds other two. If I set 'ends_at' to '13:00', it will conflict with only one event which is 'Lunch'.
To me, there are two things to implement:
make 0:00 to be treated as 23:59 when checking neighbours
throw exception if ends_at is less than starts_at (except 0:00)
Recently I've been testing package and found out that there's a bug with conflicting events.
All events within resource suddenly become conflicting and are rendered very narrowly.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: