Closed xiaohanyu closed 10 months ago
When both startDate and endDate specified, and then startDate got changed, the state of PPMonthRangePicker would be wrong.
Steps to reproduce the behavior:
startDate
dateA
endDate
dateB
dateC
dataC
There are at least 2 bugs:
minDate
https://github.com/ppresume/community/assets/1164623/3690d29c-7074-4868-b622-23500ad272e6
NA
This is a derived bug after we refactor the form with double buffering architecture.
Fixed:
https://github.com/ppresume/community/assets/1164623/d1f2a249-4805-4093-8717-af018da37e53
Description
When both startDate and endDate specified, and then startDate got changed, the state of PPMonthRangePicker would be wrong.
To Reproduce
Steps to reproduce the behavior:
startDate
todateA
andendDate
todateB
startDate
todateC
and make suredataC
is larger thandateB
Actual Behavior
There are at least 2 bugs:
endDate
has been reset to blank, however, sometimes the label still got floatedendDate
has wrongminDate
property, it still has the value ofdateA
Expected Behavior
endDate
should be reset to blank and label should not be floatedminDate
property of the MonthPicker forendDate
should be reset todateC
as well[Optional] Screenshots
Desktop
https://github.com/ppresume/community/assets/1164623/3690d29c-7074-4868-b622-23500ad272e6
Smartphone
NA
Additional Context
This is a derived bug after we refactor the form with double buffering architecture.