fix: missing types of datepicker #16334
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #16084
Some of the typings for the DatePicker component that are passed directly to flatpickr are incomplete (missing some of the possible types), meaning that Typescript can add a warning/error to a provided prop even though the value is valid to flatpickr.
Changelog
New
Changed
Testing / Reviewing
Try assigning value of type date to enable, disable , minDate and maxDate (eg : enable={[(date) => ![0, 6].includes(date.getDay())]} , minDate={new Date()}, disable={[
{
from: new Date().setDate(new Date().getDate() - 3),
to: new Date().setDate(new Date().getDate() + 3),
},
]} )
Typescript compiler should not give error.