packages/react-aria-components/docs/RangeCalendar.mdx
{/* Copyright 2020 Adobe. All rights reserved. This file is licensed to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */}
import {Layout} from '@react-spectrum/docs'; export default Layout;
import docs from 'docs:react-aria-components'; import i18nDocs from 'docs:@internationalized/date'; import statelyDocs from 'docs:@react-stately/calendar'; import {PropTable, HeaderInfo, TypeLink, PageDescription, StateTable, ContextTable} from '@react-spectrum/docs'; import styles from '@react-spectrum/docs/src/docs.css'; import packageData from 'react-aria-components/package.json'; import Anatomy from '/packages/react-aria/docs/calendar/rangecalendar-anatomy.svg'; import ChevronRight from '@spectrum-icons/workflow/ChevronRight'; import {Divider} from '@react-spectrum/divider'; import {ExampleCard} from '@react-spectrum/docs/src/ExampleCard'; import {Keyboard} from '@react-spectrum/text'; import Button from '@react-spectrum/docs/pages/assets/component-illustrations/ActionButton.svg'; import InternationalizedDate from '@react-spectrum/docs/pages/assets/component-illustrations/InternationalizedDate.svg'; import {StarterKits} from '@react-spectrum/docs/src/StarterKits';
<PageDescription>{docs.exports.RangeCalendar.description}</PageDescription>
<HeaderInfo packageData={packageData} componentNames={['RangeCalendar']} />
import {RangeCalendar, Heading, Button, CalendarGrid, CalendarCell} from 'react-aria-components';
import {ChevronLeft, ChevronRight} from 'lucide-react';
<RangeCalendar aria-label="Trip dates">
<header>
<Button slot="previous"><ChevronLeft size={20} /></Button>
<Heading />
<Button slot="next"><ChevronRight size={20} /></Button>
</header>
<CalendarGrid>
{date => <CalendarCell date={date} />}
</CalendarGrid>
</RangeCalendar>
@import "@react-aria/example-theme";
.react-aria-RangeCalendar {
width: fit-content;
max-width: 100%;
color: var(--text-color);
& header {
display: flex;
align-items: center;
margin: 0 4px .5rem 4px;
.react-aria-Heading {
flex: 1;
margin: 0;
text-align: center;
font-size: 1.375rem;
}
}
.react-aria-Button {
width: 2rem;
height: 2rem;
padding: 0;
}
& table {
border-collapse: collapse;
& td {
padding: 2px 0;
}
}
.react-aria-CalendarCell {
width: 2.286rem;
line-height: 2.286rem;
text-align: center;
border-radius: 6px;
cursor: default;
outline: none;
forced-color-adjust: none;
&[data-outside-month] {
display: none;
}
&[data-pressed] {
background: var(--gray-100);
}
&[data-focus-visible] {
outline: 2px solid var(--highlight-background);
outline-offset: -2px;
}
&[data-selected] {
background: var(--highlight-background);
color: var(--highlight-foreground);
border-radius: 0;
&[data-focus-visible] {
outline-color: var(--highlight-foreground);
outline-offset: -3px;
}
}
&[data-selection-start] {
border-start-start-radius: 6px;
border-end-start-radius: 6px;
}
&[data-selection-end] {
border-start-end-radius: 6px;
border-end-end-radius: 6px;
}
}
}
There is no standalone range calendar element in HTML. Two separate <input type="date"> elements could be used, but this is very limited in functionality, lacking in internationalization capabilities, inconsistent between browsers, and difficult to style. RangeCalendar helps achieve accessible and international range calendar components that can be styled as needed.
Read our blog post for more details about the internationalization, accessibility, and user experience features implemented by RangeCalendar.
<Anatomy role="img" aria-label="Anatomy diagram of a range calendar component, which consists of a heading, grid of cells, previous, and next buttons." />
A range calendar consists of a grouping element containing one or more date grids (e.g. months), and a previous and next button for navigating through time. Each calendar grid consists of cells containing button elements that can be pressed and navigated to using the arrow keys to select a date range. Once a start date is selected, the user can navigate to another date using the keyboard or by hovering over it, and clicking it or pressing the <Keyboard>Enter</Keyboard> key commits the selected date range.
RangeCalendar also supports an optional error message element, which can be used to provide more context about any validation errors. This is linked with the calendar via the aria-describedby attribute.
import {RangeCalendar, Heading, Button, CalendarGrid, CalendarGridHeader, CalendarHeaderCell, CalendarGridBody, CalendarCell, Text} from 'react-aria-components';
<RangeCalendar>
<Button slot="previous" />
<Heading />
<Button slot="next" />
<CalendarGrid>
<CalendarGridHeader>
{day => <CalendarHeaderCell />}
</CalendarGridHeader>
<CalendarGridBody>
{date => <CalendarCell date={date} />}
</CalendarGridBody>
</CalendarGrid>
<Text slot="errorMessage" />
</RangeCalendar>
Note that much of this anatomy is shared with non-range calendars. If you have both, the styling and internal components such as CalendarCell can be shared.
RangeCalendar makes use of the following concepts:
<ExampleCard url="../internationalized/date/index.html" title="@internationalized/date" description="Represent and manipulate dates and times in a locale-aware manner."> <InternationalizedDate /> </ExampleCard>
</section>A Calendar uses the following components, which may also be used standalone or reused in other components.
<ExampleCard url="Button.html" title="Button" description="A button allows a user to perform an action."> <Button /> </ExampleCard>
</section>To help kick-start your project, we offer starter kits that include example implementations of all React Aria components with various styling solutions. All components are fully styled, including support for dark mode, high contrast mode, and all UI states. Each starter comes with a pre-configured Storybook that you can experiment with, or use as a starting point for your own component library.
<StarterKits component="rangecalendar" />If you will use a RangeCalendar in multiple places in your app, you can wrap all of the pieces into a reusable component. This way, the DOM structure, styling code, and other logic are defined in a single place and reused everywhere to ensure consistency.
import type {RangeCalendarProps, DateValue} from 'react-aria-components';
import {Text} from 'react-aria-components';
interface MyRangeCalendarProps<T extends DateValue> extends RangeCalendarProps<T> {
errorMessage?: string
}
function MyRangeCalendar<T extends DateValue>({errorMessage, ...props}: MyRangeCalendarProps<T>) {
return (
<RangeCalendar {...props}>
<header>
<Button slot="previous"><ChevronLeft size={20} /></Button>
<Heading />
<Button slot="next"><ChevronRight size={20} /></Button>
</header>
<CalendarGrid>
{date => <CalendarCell date={date} />}
</CalendarGrid>
{errorMessage && <Text slot="errorMessage">{errorMessage}</Text>}
</RangeCalendar>
);
}
<MyRangeCalendar aria-label="Trip dates" />
A RangeCalendar has no selection by default. An initial, uncontrolled value can be provided to the RangeCalendar using the defaultValue prop. Alternatively, a controlled value can be provided using the value prop.
Date ranges are objects with start and end properties containing date values, which are provided using objects in the @internationalized/date package. This library handles correct international date manipulation across calendars, time zones, and other localization concerns.
RangeCalendar supports values with both date and time components, but only allows users to modify the dates. By default, RangeCalendar will emit <TypeLink links={i18nDocs.links} type={i18nDocs.exports.CalendarDate} /> objects in the onChange event, but if a <TypeLink links={i18nDocs.links} type={i18nDocs.exports.CalendarDateTime} /> or <TypeLink links={i18nDocs.links} type={i18nDocs.exports.ZonedDateTime} /> object is passed as the value or defaultValue, values of that type will be emitted, changing only the date and preserving the time components.
import {parseDate} from '@internationalized/date';
function Example() {
let [value, setValue] = React.useState({
start: parseDate('2020-02-03'),
end: parseDate('2020-02-12')
});
return (
<div style={{display: 'flex', gap: 20, flexWrap: 'wrap'}}>
<MyRangeCalendar
aria-label="Date range (uncontrolled)"
defaultValue={{
start: parseDate('2020-02-03'),
end: parseDate('2020-02-12')
}} />
<MyRangeCalendar
aria-label="Date range (controlled)"
value={value}
onChange={setValue} />
</div>
);
}
RangeCalendar supports selecting dates in many calendar systems used around the world, including Gregorian, Hebrew, Indian, Islamic, Buddhist, and more. Dates are automatically displayed in the appropriate calendar system for the user's locale. The calendar system can be overridden using the Unicode calendar locale extension, passed to the I18nProvider component.
Selected dates passed to onChange always use the same calendar system as the value or defaultValue prop. If no value or defaultValue is provided, then dates passed to onChange are always in the Gregorian calendar since this is the most commonly used. This means that even though the user selects dates in their local calendar system, applications are able to deal with dates from all users consistently.
The below example displays a RangeCalendar in the Hindi language, using the Indian calendar. Dates emitted from onChange are in the Gregorian calendar.
import type {DateRange} from 'react-aria-components';
import {I18nProvider} from '@react-aria/i18n';
function Example() {
let [range, setRange] = React.useState<DateRange | null>(null);
return (
<I18nProvider locale="hi-IN-u-ca-indian">
<MyRangeCalendar aria-label="Date range" value={range} onChange={setRange} />
<p>Start date: {range?.start.toString()}</p>
<p>End date: {range?.end.toString()}</p>
</I18nProvider>
);
}
RangeCalendar also supports custom calendar systems that implement custom business rules. An example would be a fiscal year calendar that follows a 4-5-4 format, where month ranges don't follow the usual Gregorian calendar.
The createCalendar prop accepts a function that returns an instance of the <TypeLink links={i18nDocs.links} type={i18nDocs.exports.Calendar} /> interface. See the @internationalized/date docs for an example implementation.
import type {AnyCalendarDate} from '@internationalized/date';
import {CalendarDate, startOfWeek, toCalendar} from '@internationalized/date';
import {GregorianCalendar} from '@internationalized/date';
function Example() {
return <MyRangeCalendar firstDayOfWeek="sun" createCalendar={() => new Custom454()} />;
}
class Custom454 extends GregorianCalendar {
// See @internationalized/date docs linked above...
///- begin collapse -///
weekPattern = [4, 5, 4, 4, 5, 4, 4, 5, 4, 4, 5, 4];
getDaysInMonth(date) {
return this.weekPattern[date.month - 1] * 7;
}
fromJulianDay(jd: number): CalendarDate {
let gregorian = super.fromJulianDay(jd);
let monthStart = startOfWeek(new CalendarDate(gregorian.year, 1, 1), 'en');
for (let months = 0; months < this.weekPattern.length; months++) {
let weeksInMonth = this.weekPattern[months];
let monthEnd = monthStart.add({weeks: weeksInMonth});
if (monthEnd.compare(gregorian) > 0) {
let days = gregorian.compare(monthStart);
return new CalendarDate(this, monthStart.year, months + 1, days + 1);
}
monthStart = monthEnd;
}
throw Error('Date is not in any month somehow!');
}
toJulianDay(date: AnyCalendarDate): number {
let monthStart = startOfWeek(new CalendarDate(date.year, 1, 1), 'en');
for (let month = 1; month < date.month; month++) {
monthStart = monthStart.add({weeks: this.weekPattern[month - 1]});
}
let gregorian = monthStart.add({days: date.day - 1});
return super.toJulianDay(gregorian);
}
getFormattableMonth(date) {
let gregorian = toCalendar(date, new GregorianCalendar());
return gregorian.set({month: date.month, day: 1});
}
isEqual(other) {
return other instanceof Custom454;
}
///- end collapse -///
}
RangeCalendar accepts an onChange prop which is triggered whenever a date is selected by the user. The example below uses onChange to update a separate element with a formatted version of the date in the user's locale. This is done by converting the date to a native JavaScript Date object to pass to the formatter.
import {getLocalTimeZone} from '@internationalized/date';
import {useDateFormatter} from '@react-aria/i18n';
function Example() {
let [range, setRange] = React.useState({
start: parseDate('2020-07-03'),
end: parseDate('2020-07-10')
});
let formatter = useDateFormatter({dateStyle: 'long'});
return (
<>
<MyRangeCalendar aria-label="Date range" value={range} onChange={setRange} />
<p>
Selected date:{' '}
{formatter.formatRange(
range.start.toDate(getLocalTimeZone()),
range.end.toDate(getLocalTimeZone())
)}
</p>
</>
);
}
Multiple CalendarGrid elements can be rendered to show multiple months at once. The visibleDuration prop should be provided to the RangeCalendar component to specify how many months are visible, and each CalendarGrid accepts an offset prop to specify its starting date relative to the first visible date.
<RangeCalendar aria-label="Trip dates" visibleDuration={{months: 3}}>
<header>
<Button slot="previous"><ChevronLeft size={20} /></Button>
<Heading />
<Button slot="next"><ChevronRight size={20} /></Button>
</header>
<div style={{display: 'flex', gap: 30, overflow: 'auto'}}>
<CalendarGrid>
{date => <CalendarCell date={date} />}
</CalendarGrid>
<CalendarGrid offset={{months: 1}}>
{date => <CalendarCell date={date} />}
</CalendarGrid>
<CalendarGrid offset={{months: 2}}>
{date => <CalendarCell date={date} />}
</CalendarGrid>
</div>
</RangeCalendar>
The pageBehavior prop allows you to control how the calendar navigates between months. By default, the calendar will navigate by visibleDuration, but by setting pageBehavior to single, pagination will be by one month.
<RangeCalendar aria-label="Trip dates" visibleDuration={{months: 3}} pageBehavior="single">
<header>
<Button slot="previous"><ChevronLeft size={20} /></Button>
<Heading />
<Button slot="next"><ChevronRight size={20} /></Button>
</header>
<div style={{display: 'flex', gap: 30, overflow: 'auto'}}>
<CalendarGrid>
{date => <CalendarCell date={date} />}
</CalendarGrid>
<CalendarGrid offset={{months: 1}}>
{date => <CalendarCell date={date} />}
</CalendarGrid>
<CalendarGrid offset={{months: 2}}>
{date => <CalendarCell date={date} />}
</CalendarGrid>
</div>
</RangeCalendar>
By default, RangeCalendar allows selecting any date range. The minValue and maxValue props can also be used to prevent the user from selecting dates outside a certain range.
This example only accepts dates after today.
import {today} from '@internationalized/date';
<MyRangeCalendar aria-label="Trip dates" minValue={today(getLocalTimeZone())} />
.react-aria-RangeCalendar {
.react-aria-CalendarCell {
&[data-disabled] {
color: var(--text-color-disabled);
}
}
}
RangeCalendar supports marking certain dates as unavailable. These dates remain focusable with the keyboard so that navigation is consistent, but cannot be selected by the user. In this example, they are displayed in red. The isDateUnavailable prop accepts a callback that is called to evaluate whether each visible date is unavailable.
Note that by default, users may not select non-contiguous ranges, i.e. ranges that contain unavailable dates within them. Once a start date is selected, enabled dates will be restricted to subsequent dates until an unavailable date is hit. See below for an example of how to allow non-contiguous ranges.
This example includes multiple unavailable date ranges, e.g. dates when a rental house is not available. The minValue prop is also used to prevent selecting dates before today.
import {today} from '@internationalized/date';
function Example() {
let now = today(getLocalTimeZone());
let disabledRanges = [
[now, now.add({days: 5})],
[now.add({days: 14}), now.add({days: 16})],
[now.add({days: 23}), now.add({days: 24})],
];
let isDateUnavailable = (date: DateValue) => disabledRanges.some((interval) => date.compare(interval[0]) >= 0 && date.compare(interval[1]) <= 0);
return <MyRangeCalendar aria-label="Trip dates" minValue={today(getLocalTimeZone())} isDateUnavailable={isDateUnavailable} />
}
.react-aria-RangeCalendar {
.react-aria-CalendarCell {
&[data-unavailable] {
text-decoration: line-through;
color: var(--invalid-color);
}
&[data-invalid] {
background: var(--invalid-color);
color: var(--highlight-foreground);
}
}
}
The allowsNonContiguousRanges prop enables a range to be selected even if there are unavailable dates in the middle. The value emitted in the onChange event will still be a single range with a start and end property, but unavailable dates will not be displayed as selected. It is up to applications to split the full selected range into multiple as needed for business logic.
This example prevents selecting weekends, but allows selecting ranges that span multiple weeks.
import {isWeekend} from '@internationalized/date';
import {useLocale} from '@react-aria/i18n';
function Example() {
let {locale} = useLocale();
return <MyRangeCalendar aria-label="Time off request" isDateUnavailable={date => isWeekend(date, locale)} allowsNonContiguousRanges />
}
RangeCalendar tries to avoid allowing the user to select invalid dates in the first place (see Validation and Unavailable dates above). However, if according to application logic a selected date range is invalid, the isInvalid prop can be set. This alerts assistive technology users that the selection is invalid, and can be used for styling purposes as well. In addition, the errorMessage slot may be used to help the user fix the issue.
This example validates that the selected date range is a maximum of 1 week in duration.
import {today} from '@internationalized/date';
function Example() {
let [range, setRange] = React.useState({
start: today(getLocalTimeZone()),
end: today(getLocalTimeZone()).add({ weeks: 1, days: 3 })
});
let isInvalid = range.end.compare(range.start) > 7;
return (
<MyRangeCalendar
aria-label="Trip dates"
value={range}
onChange={setRange}
/*- begin highlight -*/
isInvalid={isInvalid}
errorMessage={isInvalid ? 'Maximum stay duration is 1 week' : undefined}
/*- end highlight -*/
/>
);
}
.react-aria-RangeCalendar {
[slot=errorMessage] {
font-size: 12px;
color: var(--invalid-color);
}
}
By default, the first selected date is focused when a RangeCalendar first mounts. If no value or defaultValue prop is provided, then the current date is focused. However, RangeCalendar supports controlling which date is focused using the focusedValue and onFocusChange props. This also determines which month is visible. The defaultFocusedValue prop allows setting the initial focused date when the RangeCalendar first mounts, without controlling it.
This example focuses July 1, 2021 by default. The user may change the focused date, and the onFocusChange event updates the state. Clicking the button resets the focused date back to the initial value.
import {CalendarDate} from '@internationalized/date';
function Example() {
let defaultDate = new CalendarDate(2021, 7, 1);
let [focusedDate, setFocusedDate] = React.useState(defaultDate);
return (
<>
<button style={{marginBottom: 20}} onClick={() => setFocusedDate(defaultDate)}>Reset focused date</button>
<MyRangeCalendar focusedValue={focusedDate} onFocusChange={setFocusedDate} />
</>
);
}
The isDisabled boolean prop makes the RangeCalendar disabled. Cells cannot be focused or selected.
<MyRangeCalendar aria-label="Trip dates" isDisabled />
The isReadOnly boolean prop makes the RangeCalendar's value immutable. Unlike isDisabled, the RangeCalendar remains focusable.
<MyRangeCalendar aria-label="Trip dates" value={{start: today(getLocalTimeZone()), end: today(getLocalTimeZone()).add({ weeks: 1 })}} isReadOnly />
By default, the first day of the week is automatically set based on the current locale. This can be changed by setting the firstDayOfWeek prop to 'sun', 'mon', 'tue', 'wed', 'thu', 'fri', or 'sat'.
<MyRangeCalendar aria-label="Trip dates" firstDayOfWeek="mon" />
An aria-label must be provided to the RangeCalendar for accessibility. If it is labeled by a separate element, an aria-labelledby prop must be provided using the id of the labeling element instead.
In order to internationalize a RangeCalendar, a localized string should be passed to the aria-label prop. For languages that are read right-to-left (e.g. Hebrew and Arabic), keyboard navigation is automatically flipped. Ensure that your CSS accounts for this as well. Dates are automatically formatted using the current locale.
A <Heading> accepts all HTML attributes.
A <Button> accepts its contents as children. Other props such as onPress and isDisabled will be set by the RangeCalendar.
A <CalendarGrid> renders an individual month within a <RangeCalendar>. It accepts a function as its children, which is called to render a <CalendarCell> for each date. This renders a default <CalendarGridHeader>, which displays the weekday names in the column headers. This can be customized by providing a <CalendarGridHeader> and <CalendarGridBody> as children instead of a function.
A <CalendarGridHeader> renders the header within a <CalendarGrid>, displaying a list of weekday names. It accepts a function as its children, which is called with a day name abbreviation to render a <CalendarHeaderCell> for each column header.
A <CalendarHeaderCell> renders a column header within a <CalendarGridHeader>. It typically displays a weekday name.
A <CalendarGridBody> renders the body within a <CalendarGrid>. It accepts a function as its children, which is called to render a <CalendarCell> for each date.
A <CalendarCell> renders an individual date within a <CalendarGrid>.
React Aria components can be styled in many ways, including using CSS classes, inline styles, utility classes (e.g. Tailwind), CSS-in-JS (e.g. Styled Components), etc. By default, all components include a builtin className attribute which can be targeted using CSS selectors. These follow the react-aria-ComponentName naming convention.
.react-aria-RangeCalendar {
/* ... */
}
A custom className can also be specified on any component. This overrides the default className provided by React Aria with your own.
<CalendarGrid className="my-calendar-grid">
</CalendarGrid>
In addition, some components support multiple UI states (e.g. focused, placeholder, readonly, etc.). React Aria components expose states using data attributes, which you can target in CSS selectors. For example:
.react-aria-CalendarCell[data-selected] {
/* ... */
}
.react-aria-CalendarCell[data-invalid] {
/* ... */
}
The className and style props also accept functions which receive states for styling. This lets you dynamically determine the classes or styles to apply, which is useful when using utility CSS libraries like Tailwind.
<CalendarCell className={({isSelected}) => isSelected ? 'bg-blue-600' : 'bg-gray-600'} />
Render props may also be used as children to alter what elements are rendered based on the current state. For example, you could add an additional element when a date is unavailable.
<CalendarCell>
{({formattedDate, isUnavailable}) => (
<>
{isUnavailable && <UnavailableIcon />}
<span>{formattedDate}</span>
</>
)}
</CalendarCell>
The states, selectors, and render props for each component used in a RangeCalendar are documented below.
A RangeCalendar can be targeted with the .react-aria-RangeCalendar CSS selector, or by overriding with a custom className. It supports the following states and render props:
A Button can be targeted with the .react-aria-Button CSS selector, or by overriding with a custom className. The next and previous buttons can be targeted specifically with the [slot=previous] and [slot=next] selectors. Buttons support the following states:
A CalendarGrid can be targeted with the .react-aria-CalendarGrid CSS selector, or by overriding with a custom className. When a function is provided as children, a default <CalendarGridHeader> and <CalendarGridBody> are rendered. If you need to customize the styling of the header cells, you can render them yourself.
import {CalendarGridHeader, CalendarHeaderCell, CalendarGridBody} from 'react-aria-components';
<RangeCalendar aria-label="Trip dates">
<header>
<Button slot="previous"><ChevronLeft size={20} /></Button>
<Heading />
<Button slot="next"><ChevronRight size={20} /></Button>
</header>
<CalendarGrid>
<CalendarGridHeader>
{day => <CalendarHeaderCell style={{color: 'var(--blue)'}}>{day}</CalendarHeaderCell>}
</CalendarGridHeader>
<CalendarGridBody>
{date => <CalendarCell date={date} />}
</CalendarGridBody>
</CalendarGrid>
</RangeCalendar>
A CalendarGridHeader can be targeted with the .react-aria-CalendarGridHeader CSS selector, or by overriding with a custom className.
A CalendarHeaderCell can be targeted with the .react-aria-CalendarHeaderCell CSS selector, or by overriding with a custom className.
A CalendarGridBody can be targeted with the .react-aria-CalendarGridBody CSS selector, or by overriding with a custom className.
A CalendarCell can be targeted with the .react-aria-CalendarCell CSS selector, or by overriding with a custom className. It supports the following states:
The error message element within a RangeCalendar can be targeted with the [slot=errorMessage] CSS selector, or by adding a custom className.
If you need to customize one of the components within a RangeCalendar, such as CalendarGrid or CalendarCell, in many cases you can create a wrapper component. This lets you customize the props passed to the component.
function MyCalendarCell(props) {
return <CalendarCell {...props} className="my-item" />
}
All React Aria Components export a corresponding context that can be used to send props to them from a parent element. This enables you to build your own compositional APIs similar to those found in React Aria Components itself. You can send any prop or ref via context that you could pass to the corresponding component. The local props and ref on the component are merged with the ones passed via context, with the local props taking precedence (following the rules documented in mergeProps).
<ContextTable components={['RangeCalendar']} docs={docs} />
This example uses RangeCalendarContext to create a composite component containing a calendar and buttons representing preset dates. The <TypeLink links={docs.links} type={docs.exports.useSlottedContext} /> hook can be used to consume contexts that support the slot prop.
import {RangeCalendarContext, useSlottedContext} from 'react-aria-components';
function CalendarPicker({children}) {
let [value, onChange] = React.useState(null);
let [focusedValue, onFocusChange] = React.useState(null);
return (
/*- begin highlight -*/
<RangeCalendarContext.Provider value={{value, onChange, focusedValue, onFocusChange}}>
<div className="calendar-picker">
{children}
</div>
</RangeCalendarContext.Provider>
);
}
interface PresetProps {
value: {start: CalendarDate, end: CalendarDate},
children: React.ReactNode
}
function Preset({value, children}: PresetProps) {
/*- begin highlight -*/
let context = useSlottedContext(RangeCalendarContext)!;
/*- end highlight -*/
let onPress = () => {
context.onFocusChange(value.start);
context.onChange(value);
};
return (
<Button onPress={onPress}>{children}</Button>
);
}
Now you can combine a RangeCalendar and one or more Preset components in a CalendarPicker.
import {startOfWeek, endOfWeek, startOfMonth, endOfMonth} from '@internationalized/date';
import {useLocale} from 'react-aria';
function Example() {
let {locale} = useLocale();
let now = today(getLocalTimeZone());
let nextMonth = now.add({months: 1});
return (
<CalendarPicker>
<Preset value={{start: startOfMonth(now), end: endOfMonth(now)}}>This month</Preset>
<Preset value={{start: startOfWeek(now, locale), end: endOfWeek(now, locale)}}>This week</Preset>
<Preset value={{start: startOfMonth(nextMonth), end: endOfMonth(nextMonth)}}>Next month</Preset>
<MyRangeCalendar aria-label="Date filter" />
</CalendarPicker>
);
}
.calendar-picker {
> .react-aria-Button {
margin: 0 4px 8px 4px;
}
}
RangeCalendar passes props to its child components, such as the heading and buttons, via their associated contexts. These contexts are exported so you can also consume them in your own custom components. This enables you to reuse existing components from your app or component library together with React Aria Components.
<ContextTable components={['Heading', 'Button', 'Text']} docs={docs} />
This example consumes from HeadingContext in an existing styled heading component to make it compatible with React Aria Components. The <TypeLink links={docs.links} type={docs.exports.useContextProps} /> hook merges the local props and ref with the ones provided via context by RangeCalendar.
import type {HeadingProps} from 'react-aria-components';
import {HeadingContext, useContextProps} from 'react-aria-components';
const MyCustomHeading = React.forwardRef((props: HeadingProps, ref: React.ForwardedRef<HTMLHeadingElement>) => {
// Merge the local props and ref with the ones provided via context.
///- begin highlight -///
[props, ref] = useContextProps(props, ref, HeadingContext);
///- end highlight -///
// ... your existing Heading component
return <h2 {...props} ref={ref} />;
});
Now you can use MyCustomHeading within a RangeCalendar, in place of the builtin React Aria Components Heading.
<RangeCalendar>
<MyCustomHeading />
</RangeCalendar>
RangeCalendar provides a <TypeLink links={statelyDocs.links} type={statelyDocs.exports.RangeCalendarState} /> object to its children via RangeCalendarStateContext. This can be used to access and manipulate the calendar's state.
This example shows a RangeCalendarValue component that can be placed within a RangeCalendar to display the currently selected date as a formatted string.
import {RangeCalendarStateContext} from 'react-aria-components';
import {useDateFormatter} from 'react-aria';
function RangeCalendarValue() {
/*- begin highlight -*/
let state = React.useContext(RangeCalendarStateContext)!;
/*- end highlight -*/
let start = state.value?.start.toDate(getLocalTimeZone());
let end = state.value?.end.toDate(getLocalTimeZone());
let formatted = start && end ? useDateFormatter().formatRange(start, end) : 'None';
return <small>Selected date range: {formatted}</small>;
}
<RangeCalendar>
<header>
<Button slot="previous"><ChevronLeft size={20} /></Button>
<Heading />
<Button slot="next"><ChevronRight size={20} /></Button>
</header>
<CalendarGrid>
{date => <CalendarCell date={date} />}
</CalendarGrid>
<RangeCalendarValue />
</RangeCalendar>
If you need to customize things even further, such as accessing internal state or customizing DOM structure, you can drop down to the lower level Hook-based API. See useRangeCalendar for more details.