fix(Picker): should reset the second argument when the first argument…

[JerryWu1234]

… is changed somehow

fixes: #13365

we should reset the second argument when the first argument is changed.

Before submitting a pull request, please read the contributing guide.

在提交 pull request 之前，请阅读 贡献指南。

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.77%. Comparing base (ec5b45b) to head (db5f4b0).
Report is 48 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #13366      +/-   ##
==========================================
+ Coverage   89.60%   89.77%   +0.16%     
==========================================
  Files         257      257              
  Lines        7013     7021       +8     
  Branches     1736     1738       +2     
==========================================
+ Hits         6284     6303      +19     
+ Misses        384      378       -6     
+ Partials      345      340       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[JerryWu1234]

@inottn Please help to review. I done and fixed all fail tests .

[inottn]

I don't know if the previous interactions were intentional; if there is an issue, the onChange logic might need to be modified. If I have time, I will see how to adjust it.

[JerryWu1234]

I don't know if the previous interactions were intentional; if there is an issue, the onChange logic might need to be modified. If I have time, I will see how to adjust it.

I definitely sure that it wasn't intentional. and it is a bug.
I would like do it if you are busy.

[JerryWu1234]

thanks for point out.
now no Area component error, and added edge case.
please help to review it again
@inottn

[chenjiahan]

I prefer to keep the current behavior. If we reset the option it will break the user experience of date picker or time picker.

[JerryWu1234]

I prefer to keep the current behavior. If we reset the option it will break the user experience of date picker or time picker.

ok, if we keep the current behavior.
Is there another workaround to fix it?
@chenjiahan

[chenjiahan]

How about adding a new prop to enable this new behavior? Such as resetChildren.

[JerryWu1234]

How about adding a new prop to enable this new behavior? Such as resetChildren.

I think the default should be false if we add a new prop.