No effect applied when using min
and max
properties on mode="range"
in v9.0.8
#2432
Unanswered
vildantursic
asked this question in
Support
Replies: 1 comment
-
Hi @vildantursic in the previous version of DayPicker, we were indeed disabling dates when they could not belong to the selected range. This behavior caused some confusion and we removed it in v9. Is what you are referring to? I think your solution of implementing a |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Code
Expected Behavior
Max should disable dates after x days from selected date. So if I select
1.1.2024.
and max is4
last date that I should be able to select is1.4.2024.
.Actual Behavior
All dates are available for selection
Temporary solution
Add another object in
disabled
list{ after: add(dateRange.from || new Date(), { days: DATE_RANGE_LIMIT - 1 }), before: dateRange.from }
which will disable dates after selected item.Beta Was this translation helpful? Give feedback.
All reactions