Migration
Map common date-picker concepts to Calix.
Calix uses value and onChange consistently across its components. It exposes
native Date values and range objects, and keeps calendar-specific behavior in
the adapter prop.
From react-day-picker
| react-day-picker | Calix |
|---|---|
<DayPicker mode="single" /> | <Calendar mode="single" /> |
selected / onSelect | value / onChange |
disabled={matchers} | minDate, maxDate, disabledDates, disabledWeekdays, or isDateDisabled |
numberOfMonths | numberOfMonths |
classNames | classNames plus the data-* state contract |
Add adapter={gregorian} to the Calix component. Unlike react-day-picker,
Calix includes a popup DatePicker and a Jalali adapter.
From MUI X, Ant Design, or Mantine
These libraries couple calendar UI to their component systems. With Calix, choose one of three migration paths:
- import
@alydev/themes/default.cssfor a ready appearance; - attach your existing utility/CSS classes with
classNames; - render entirely custom markup with
useCalendar.
The form value mapping is usually direct:
For ranges, initialize with { start: null, end: null }. Use onOutputChange
and outputPattern only when an external API needs a serialized value.
Add Jalali without a separate picker
Replace the adapter and locale; selection and styling APIs stay the same.
Review Localization if your previous picker used custom Persian labels, week starts, or digit formatting.