We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch [email protected] for the project I'm working on.
[email protected]
The problem I faced is the same as these issues:
This happens in the month view, when there are:
That event does not get rendered for the other days it spans unless it is among the first few events (including the + [n] show more) to be truncated.
Here is the diff that solved my problem:
diff --git a/node_modules/react-big-calendar/dist/react-big-calendar.esm.js b/node_modules/react-big-calendar/dist/react-big-calendar.esm.js index 771b698..4fa6c41 100644 --- a/node_modules/react-big-calendar/dist/react-big-calendar.esm.js +++ b/node_modules/react-big-calendar/dist/react-big-calendar.esm.js @@ -1646,7 +1646,7 @@ var EventEndingRow = /*#__PURE__*/function (_React$Component) { var _this$props = this.props, segments = _this$props.segments, slots = _this$props.slotMetrics.slots; - var rowSegments = eventLevels(segments).levels[0]; + var rowSegments = segments; var current = 1, lastEnd = 1, row = [];
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch
[email protected]
for the project I'm working on.The problem I faced is the same as these issues:
This happens in the month view, when there are:
That event does not get rendered for the other days it spans unless it is among the first few events (including the + [n] show more) to be truncated.
Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: