chakra-dayzed-datepicker
chakra-dayzed-datepicker copied to clipboard
the default state for range picker.
I made an immature decision to let the range state as an array [startDate, endDate]
, this will cause some issues when doing state management.
My original intent is to have a empty object if user don't provide their own:
{
startDate: undefined,
endDate: undefined
}
but it will break range usage from previous versions.
I like this. It's more explicit. Caret ranges won't auto-increment "minor" versions before 1.0, (link) so it shouldn't cause users a problem until they explicitly update, as long as this is done with a "minor" change (such as 0.22 to 0.23) rather than "patch" change (such as 0.22.0 to 0.22.1).