fix: fix dayjs localizer merge function to not change min and max #2712
Conversation
|
@cutterbl this would be a big help in our production app, if you're able to take a peek! |
|
Any chance we can get this merged @cutterbl ? :) |
|
Would appreciate a merge! Thanks @cutterbl Hope this will fix issue shown in image... |
## [1.19.2](v1.19.1...v1.19.2) (2025-05-28) ### Bug Fixes * fix dayjs localizer merge function to not change min and max upon tz change ([#2712](#2712)) ([7d2aa77](7d2aa77))
|
🎉 This PR is included in version 1.19.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
Hello guys, I guess this PR causes this problem: On localhost, the time slots match min/max I pass to component's prop But it displays wrong when I build it on to production I think this is because production uses version 1.19.2, while on localhost I use 1.15.0 (I don't install with lockfile immutable) If I inspect the outer component, I see localhost props and production props are the same, which means there's some internal conversion that makes the time display wrong I can confirm version 1.15.0 don't have this, I've revert the code and it works well |
Fixes #2688
Fixes dayjs localizer merge function so min and max of the day stays always the same.