Skip to content

Incorrect minute handling with luxonLocalizer and step set to 1 #2361

Closed
@pdady

Description

@pdady

Check that this is really a bug

  • I confirm

Reproduction link

https://codesandbox.io/s/react-big-calendar-example-forked-vdkr95?file=/src/App.js

Bug description

The luxonLocalizer is causing events with start time that have seconds greater than 30 to be displayed in the next minute instead of being displayed in the same minute as their start time. This issue is visible when the step is set to 1.

Expected Behavior

The event should start in the same minute as the start time, similar to other Localizers.

image

Actual Behavior

Event with seconds of start greater than 30 are being moved in the next minute.

image

react-big-calendar version

1.6.3

React version

18.2.0

Platform/Target and Browser Versions

All

Validations

  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • Make sure this is a react-big-calendar issue and not an implementation issue

Would you like to open a PR for this bug?

  • I'm willing to open a PR

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions