-
Notifications
You must be signed in to change notification settings - Fork 1k
feat: set new hours considering the offset #6424
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
I still need to change on grommet/src/js/components/Calendar/utils.js |
@matheushahnn First, thank you for picking this issue up.
This is actually performing as expected. I flagged this as an opportunity to consolidate logic as it looked like we are doing something somewhat related to the timezone offset work, but in a slightly different manner and didn't know if would be beneficial to bring consistency here. I did not study closely. If your judgement and recommendation is that this should remain as is, please let us know. The rest of the work is looking great, thank you. |
I think we can keep it as it is. |
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.
Looks good!
What does this PR do?
It fixes the issue related to timezone on Calendar
Closes #6421
Where should the reviewer start?
What testing has been done on this PR?
How should this be manually tested?
Test this storybook https://storybook.grommet.io/?path=/story/input-dateinput-format-inline--format-inline
Do Jest tests follow these best practices?
screen
is used for querying.userEvent
is used in place offireEvent
.asFragment()
is used for snapshot testing.Any background context you want to provide?
What are the relevant issues?
#6421
Screenshots (if appropriate)
Do the grommet docs need to be updated?
Should this PR be mentioned in the release notes?
Is this change backwards compatible or is it a breaking change?