-
Notifications
You must be signed in to change notification settings - Fork 228
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
Bump @fullcalendar/* from 4.3.0 to 5.0.0 beta #2196
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2196 +/- ##
=============================================
+ Coverage 30.36% 94.41% +64.04%
Complexity 103 103
=============================================
Files 146 7 -139
Lines 5354 394 -4960
Branches 802 0 -802
=============================================
- Hits 1626 372 -1254
+ Misses 3728 22 -3706
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
f937ad2
to
0c5b2cd
Compare
Sudden build errors most likely related to an upstream change: fullcalendar/fullcalendar#5467 |
0c5b2cd
to
03209bb
Compare
9e180f1
to
fa3458f
Compare
Signed-off-by: Georg Ehrke <developer@georgehrke.com>
Signed-off-by: Georg Ehrke <developer@georgehrke.com>
fa3458f
to
f8c020e
Compare
Replaced by #2498 |
Plenty of features (#26, #30, #39, #152, #1844) for the next 2.1 Milestone are closely related to FullCalendar. So instead of implementing them for FullCalendar 4 and then having to redo a lot of the work for FullCalendar 5, i would like to update to FullCalendar 5 first.
According to https://fullcalendar.io/blog/2020/04/v5-beta-released, the final release will be Early or Mid May.
ToDo
With FullCalendar 5,
box-sizing: border-box
becomes the standard in fc, so updating will also fix #1815 :)