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
I am using minDate={moment()} to prevent users selecting dates in the past and have no limit on future dates.
If they want to change the year and select 2021, they have no way of getting back to 2020 without going back through all the months.
With minDate={moment()}
Without minDate={moment()}
The text was updated successfully, but these errors were encountered:
I may work on this.
Regardless of if I get around to it, the immediate question is:
Should it display 5 full rows of years (2020-2034), or stick with 7 future years (2020-2027)?
The former feels like too many (over a decade) and the latter would still leave a gap.
I've not looked at the code yet but, if possible, I would use a flex grid and set the columns to 3. Then, at the very least, the gap would be at the end. This would also allow the display to adapt for if the dev were to set a maxDate.
I think the simplest solution for now would be to just have the same count of years for all representations. So a full decade even thought it seems like a lot. We'll be refactoring this component next year so there will be more time to investigate options then.
I am using
minDate={moment()}
to prevent users selecting dates in the past and have no limit on future dates.If they want to change the year and select 2021, they have no way of getting back to 2020 without going back through all the months.
With
minDate={moment()}
Without
minDate={moment()}
The text was updated successfully, but these errors were encountered: