Update to @date-io v1.0 caused breaking changes to Calendar
See original GitHub issueThe update in this commit: #846
Seems to have caused a breaking change in Calendar due to the name change of the util method from startOfMonth
to getStartOfMonth
.
Looks like this update requires users to also manually update their @date-io version (since that dependency isn’t included in the package).
Just wanted to point this out as something you might want to mention in docs and changelogs!
We had to spend a morning debugging a break to one of our deployed instances, and it would have helped to find some documentation here about it.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Update to @date-io v1.0 caused breaking changes to Calendar
Seems to have caused a breaking change in Calendar due to the name change of the util method from startOfMonth to getStartOfMonth ....
Read more >v1.0 - V-Calendar
This is a big update with quite a few breaking changes. Here are the biggest updates. Responsive Layouts; i18n Improvements; Modern Design; Theming...
Read more >Known issues with Microsoft Graph
This article describes known issues and limitations with Microsoft Graph and provides workarounds when possible.
Read more >Deprecations by version - GitLab Docs
Each deprecated feature will be removed in a future release. Some features cause breaking changes when they are removed. To be notified of...
Read more >Migrating from v4 to v5 - Gatsby
Updating community plugins. Handling breaking changes. Minimal Node.js version 18.0.0; Minimal required React version is 18; Non-ESM browsers are not ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, I see now. It’s listed as a “Feature”.
It probably would be nice to mention that it is a breaking change. Most people don’t expect minor version updates to cause their production apps to crash
Exactly, a breaking change is a breaking change, should result in major version bump