Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Drag and Drop not functioning properly and duplicating events #2582

Open
5 tasks done
OnsKharrat06 opened this issue Apr 26, 2024 · 1 comment · May be fixed by #2593
Open
5 tasks done

Bug: Drag and Drop not functioning properly and duplicating events #2582

OnsKharrat06 opened this issue Apr 26, 2024 · 1 comment · May be fixed by #2593
Labels

Comments

@OnsKharrat06
Copy link
Contributor

Check that this is really a bug

  • I confirm

Reproduction link

https://jquense.github.io/react-big-calendar/examples/index.html?path=/docs/addons-drag-and-drop--example-2

Bug description

Hello community,

It came to my attention that in the resources Drag and Drop (under ADDONS/ Drag and Drop/ Props), there is a checkbox with the following option (Keep copy of dragged "source" event in its original resource slot). Despite unchecking this option, the drugged events keep on duplicating without deleting the old event.

As shown in the recording below, the more we move the event, the more duplications get created.

bug_drag.and.drop.mov

Expected Behavior

The expected behavior should be to move the event from one time slot to another without duplications.

Actual Behavior

The current behavior is that the event is getting duplicated as we move it from one time slot to another. The required drag and drop behavior is not applied.

react-big-calendar version

1.11.3

React version

18.2.0

Platform/Target and Browser Versions

macOS

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
@geraldhoxha95
Copy link

@OnsKharrat06 have you started working on a fix for this? I can look into it if not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants