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
While I do like having one DateInput component with the range prop, lets just add the single DateInput component for now and we can refactor/merge them later on
Currently, DateRange relies on the Bits UIRange Calendar. This implementation could be refactored to handle single dates, enabling functionality similar to the Bits UIDate Picker, which is designed for single-date selection.
To achieve this, we could create a new DateInput component derived from DateRange. The initial state would handle single dates, with a prop allowing it to switch back to the full DateRange functionality, all within the DateInput interface.
For backward compatibility, the existing DateRange component would remain unchanged for current users, while any new features and improvements would be incorporated into DateInput.
Like DateRange but just for one date.
I think there is a possible rationale to allow
that is just an alias for the DateRange component
The text was updated successfully, but these errors were encountered: