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
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.
Check that this is really a bug
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
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: