-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[pickers] Fix AdapterDayjs timezone behavior
#13362
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
Conversation
|
Deploy preview: https://deploy-preview-13362--material-ui-x.netlify.app/ Updated pages: |
|
@LukasTy out of curiosity, what required a e2e test here rather than a unit test? |
I failed to trigger this case in a unit test. |
|
OK 👌 |
flaviendelangle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great fix!
Fixes #13290
The main problem was that in an environment, where
utcandtimezoneplugins are enabled, but regular dayjs constructor is used, changing value could have resulted in timezone differences.Steps to reproduce
Before
https://codesandbox.io/p/sandbox/adapterdayjs-daterangepicker-timezone-error-lqdjgx?file=%2Fsrc%2FApp.tsx
After
https://codesandbox.io/p/sandbox/adapterdayjs-daterangepicker-timezone-error-fixed-hcz288?file=%2Fsrc%2FApp.tsx