You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems the bug appears when minDate is set, but the maxDate is not set (or when maxDate is set, but minDate not)
and it is later fixed with: #2307
However, the pull request is merged few days after the RC.9 release
and it is part of the last "next" tag release (0.0.0-155f8e0a7)
Describe the bug
DatePicker crashes when dealing with future years
To reproduce
Click on the datepicker in the codesandbox
Isolated example
https://codesandbox.io/s/wonderful-hooks-ip6r5?file=/src/App.js
Expected behavior
I expect the datepicker not to crash.
Screenshots
If applicable, add screenshots to help explain your problem.
Context
Affected components (if known)
Log output / Any errors in the console
Organization: (if applicable)
Priority: (optional) (Low, Medium, High or Very High)
Setting priority would indicate the importance of the issue
and would help the process of dispatching and processing.
To set the appropriate priority, you need to consider the impact
and if the issue:
Note: the priority would be re-evaluated by the issue processors, according to the project internal criterias
Business impact: very high (dealing with future years is a common use case for us). Can't upgrade to latest version if this is not fixed for us.
The text was updated successfully, but these errors were encountered: