-
Notifications
You must be signed in to change notification settings - Fork 733
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
Bugfix- birth year selction on profile edit page #11337
Bugfix- birth year selction on profile edit page #11337
Conversation
Hi @haldaranup - thanks, this definitely looks like the right fix! I think we would like to include this in our upcoming release, so if I could ask you to rebase this PR onto release-v0.16.x that would be great. To do this, I would suggest the following workflow:
|
15ce825
to
595ff11
Compare
Thanks @rtibbles, I have done the steps mentioned above. Please let me know if any other changes are required or if anything is done incorrectly |
Looks right to me, thank you! We will do a full review on Monday. |
Build Artifacts
|
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.
Code looks good and manual testing checks out - the value of the component and the label match! Could you fix the line length for your comments, so we can merge?
LGTM as well, no issues observed while manually testing. |
Thank you for your contribution @haldaranup! |
Summary
After selecting birth year the value gets mismatched because of incorrect label. This is because of timezone, when localized in any timezone that is less than UTC, ex-
new Date('2023')
the date will be shown 2022 instead of 2023So, instead of passing year directly to
$fomatDate
('2023'), setting full year to it so there is no effect of timezone…
References
Fixes #11292
…
Reviewer guidance
…
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)