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

Avoid wwo events sharing one time overlap #2302

Closed
5 tasks done
Canopix opened this issue Nov 11, 2022 · 2 comments
Closed
5 tasks done

Avoid wwo events sharing one time overlap #2302

Canopix opened this issue Nov 11, 2022 · 2 comments
Labels

Comments

@Canopix
Copy link

Canopix commented Nov 11, 2022

Check that this is really a bug

  • I confirm

Reproduction link

Bug description

I have two events that share only one time:

Event A: Finish at 4 PM
Event B: Start at 4 PM

The events are being split in the calendar and are not needed.

How avoid this?
image

Expected Behavior

No response

Actual Behavior

No response

react-big-calendar version

React version

=-

Platform/Target and Browser Versions

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
@Canopix Canopix added the bug label Nov 11, 2022
@bu6n
Copy link
Contributor

bu6n commented Nov 14, 2022

There already similar issues to this problem. Would #1530 help for example?

@Canopix
Copy link
Author

Canopix commented May 3, 2023

Hey everyone!
image

Just wanted to give you all a quick update on my react-big-calendar issue. Thanks to the awesome folks in this Github issue, I was able to solve the problem of overlapping events by tweaking the minimumStartDifference with the overlap function.

I really appreciate all the help and support from the community. Your suggestions and solutions made a huge difference, and I can't thank you enough for your time and effort in helping me out.

Hope this solution will be helpful for others who run into similar issues in the future.

Thanks again, you guys rock!

@Canopix Canopix closed this as completed May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants