Creating a better date-picking experience with the DateRangePicker component
Published: 2022-01-13 22:15:11

When crafting a search interface, it's often enough to use what comes prepackaged with Algolia's InstantSearch libraries. Each library comes in a different flavor of JavaScript for your ease of use. Each one has all the main pieces you need to craft a strong UI. 

Sometimes you want to go beyond what's available. 

At that point, you're presented with two options: craft your own with our connector APIs or find a pre-built custom widget.

It should come as no surprise to anyone that knows me that when presented with wanting a React date picker for [December's coding challenge,](https://www.algolia.com/blog/engineering/algolia-coding-challenge-help-santa/) I wanted to write as little code as possible to make it work, but I also wanted the best UI possible for Santa. When it came to bonus challenge number 5, I needed something extra. My first stop? [The Algolia Code Exchange](https://www.algolia.com/developers/code-exchange/)!

After a quick search around `date` components, I found exactly what I needed: the aptly-named [@algolia/react-instantsearch-widget-date-range-picker](https://github.com/algolia/react-instantsearch-widget-date-range-picker)!

## Setting up the project

If you'd like to follow along, you'll need to install a new React InstantSearch project. The easiest way to do that is to run the following command:

```sh
 npx create-instantsearch-app concert-search \
 --app-id latency \
 --api-key 059c79ddd276568e990286944276464a \
 --index-name concert_events_instantsearchjs \
 --template "React InstantSearch"
```

This monster command will set up a React InstantSearch project and connect it to [Algolia's hosted concert Index](https://github.com/algolia/datasets/tree/master/concerts). Change directory into the created folder and run `yarn start` for a solid starting point.

At this point, you've got a full search experience for a set of concerts. 

If you want to filter by date, you could set up a `<RefinementList>` component and set its `attribute` prop to `date`, but those dates are Unix timestamps (for easiest comparisons). This isn't ideal for the user experience. Let's make that better.

## Installing and configuring the widget

To get the date range picker up and running, we need to install a couple of dependencies. 
```bash
npm install @algolia/react-instantsearch-widget-date-range-picker @duetds/date-picker
```

This will install the official Algolia React Date picker widget and its dependency the Duet Date picker.

From here, we need to import the packages into our `src/App.js` file and initialize the Duet Date Picker for use.

```javascript

// Add right after the imports included in the create-instantsearch-app code

import { DateRangePicker } from '@algolia/react-instantsearch-widget-date-range-picker';  
import { defineCustomElements } from "@duetds/date-picker/dist/loader";

// Defines the custom elements from the date picker for use on the window object  
defineCustomElements(window);
```

Now that these packages are imported, we're ready to get this on the page.

## Adding the date range picker

To add the picker to the page, we need to select a spot within the `<InstantSearch>` component. The base of the app is a `search-panel`. By default, all we have inside this is the results, but we can add a filter panel, as well.

```javascript

<InstantSearch _searchClient_={searchClient} indexName="concert_events_instantsearchjs">  
  <div className="search-panel">  
    <div className="search-panel__filters">  
      <DateRangePicker attribute="date" />  
    </div>  

    <div _className_="search-panel__results">

      //... Results code

    </div>
  </div>
</InstantSearch>
```

The DateRangePicker accepts an `attribute` prop. This prop accepts a date-based attribute from the hits in our Index. 

_Quick note_: The DateRangePicker accepts a Unix timestamp with milliseconds since the Epoch, not seconds. Depending on your data structure, you may need to create a secondary timestamp in your data.

When you view the rendered page, you should now have a date picker. There are a few small UI snags to clean up. 

The Duet Date picker uses a slew of CSS Custom Properties for much of its styling. At the start of our `src/App.css` file, we need to paste those in and configure for our app (as appropriate).

```css

:root {  
  --duet-color-primary: #3c4ee0;  
  --duet-color-text: #333;  
  --duet-color-text-active: #fff;  
  --duet-color-placeholder: #666;  
  --duet-color-button: #f5f5f5;  
  --duet-color-surface: #fff;  
  --duet-color-overlay: rgba(0, 0, 0, 0.8);  
  --duet-color-border: #d6d6e7;  

  --duet-font: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica,  
  Arial, sans-serif;  
  --duet-font-normal: 400;  
  --duet-font-bold: 600;  

  --duet-radius: 3px;  
  --duet-z-index: 600;  
}

```

The two picker areas are a little close together still, so let's fix that with a little CSS, as well. This can go in `src/App.css` but should be closer to the bottom. There are many ways to get the space between the two items, the quick and easy solution is to use CSS Grid and the `gap` property.

```css

.date-range-picker {  
  display: grid;  
  gap: 1rem;  
}  
```

And with that, we have a functioning, user-friendly date picker. No more dealing with Unix timestamps and conversions.

## Take this further

This works great in the small sample dataset, but can also be brought into any Algolia InstantSearch application. If you're looking to take this example further, create a better UI around each Hit by editing the hit component in `src/App.js`. You could also show the current filters applied with the [CurrentRefinements component](https://www.algolia.com/doc/api-reference/widgets/current-refinements/react/).