Not filling whole timeslot expands event for another timeslot

[KrallXZ]

Do you want to request a feature or report a bug?

Report a bug

What's the current behavior?

All of these events should start at 10:00, but the darkblue one is stretched for 1 whole timecell, so its height is now (1 timecell + expected height) and starts 1 timeslot before expecting start.
Green lasts for 1,5 timecell, darkblue for 2/3 timecell and lightblue for 1 timecell, so this happens only when not whole timecell is filled, but when It's at least 1 timecell it works like expected.

<BigCalendar
            localizer={localizer}
            events={mappedEvents}
            defaultView={Views.DAY}
            step={30}
            timeslots={1}
            resources={mappedEmployees}
            defaultDate={moment(day).toDate()}
            views={[Views.DAY]}
            min={new Date(moment('5:30', 'H:mm'))}
            max={new Date(moment('19:00', 'H:mm'))}
            toolbar={false}
            onSelectEvent={handleEventSelection}
          />

What's the expected behavior?

They all should start at 10:00 and last for correct time.

[vAskitsa]

I recently update to rbc version 0.22.0 and struggle with same problems. My one timeslot is 30 minutes and step is 15 minutes. When i try to render events shorter than step i get problems. Any solutions?

[stianeikeland]

This is the same issue as: #1396
Seems like it was caused by a change added in #1381

[KrallXZ]

It looks like #1447 should fix it, but I still have same behavior like in first post.

[milinpaul]

@KrallXZ How did you make different colors for different events with highlighted in the start.
Appreciate you help.

[KhaledMohamedP]

@KrallXZ @v1k45

can you check if this pending PR fixes your issue #1473 ?

We are waiting for the maintainer to review and merge this PR soon 😄

[KrallXZ]

@KhaledMohamedP It's still the same.

[vAskitsa]

Unfortunately rearrangement algorithm does not solve this pretty serious problem. Still same behavior.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stianeikeland]

Still an issue, please don’t close dear stalebot

[vAskitsa]

Yes, still a big issue.