Primitives to build simple, flexible, WAI-ARIA compliant React autocomplete/dropdown/select/combobox components

You need an autocomplete/dropdown/select experience in your application and you want it to be accessible. You also want it to be simple and flexible to account for your use cases.

This is a component that controls user interactions and state for you so you can create autocomplete/dropdown/select/etc. components. It uses a render function as children which gives you maximum flexibility with a minimal API because you are responsible for the rendering of everything and you simply apply props to what you're rendering.

This differs from other solutions which render things for their use case and then expose many options to allow for extensibility resulting in a bigger API that is less flexible as well as making the implementation more complicated and harder to contribute to.

NOTE: The original use case of this component is autocomplete, however the API is powerful and flexible enough to build things like dropdowns as well.

• Installation
• Usage
• Props
• Control Props
• Child Callback Function
• Examples
• Inspiration
• Other Solutions
• Contributors
• LICENSE

This module is distributed via npm which is bundled with node and should be installed as one of your project's dependencies:

npm install --save downshift

This package also depends on react and prop-types. Please make sure you have those installed as well.

Note also this library supports preact out of the box. If you are using preact then look in the dist/ folder and use the module you want with the preact suffix.

import Downshift from 'downshift'

function BasicAutocomplete({items, onChange}) {
  return (
    <Downshift onChange={onChange}>
      {({
        getInputProps,
        getItemProps,
        isOpen,
        inputValue,
        selectedItem,
        highlightedIndex
      }) => (
        <div>
          <input {...getInputProps({placeholder: 'Favorite color ?'})} />
          {isOpen ? (
            <div style={{border: '1px solid #ccc'}}>
              {items
                .filter(
                  i =>
                    !inputValue ||
                    i.toLowerCase().includes(inputValue.toLowerCase()),
                )
                .map((item, index) => (
                  <div
                    {...getItemProps({item})}
                    key={item}
                    style={{
                      backgroundColor:
                        highlightedIndex === index ? 'gray' : 'white',
                      fontWeight: selectedItem === item ? 'bold' : 'normal',
                    }}
                  >
                    {item}
                  </div>
                ))}
            </div>
          ) : null}
        </div>
      )}
    </Downshift>
  )
}

function App() {
  return (
    <BasicAutocomplete
      items={['apple', 'orange', 'carrot']}
      onChange={selectedItem => console.log(selectedItem)}
    />
  )
}

downshift is the only component. It doesn't render anything itself, it just calls the child function and renders that. Wrap everything in <Downshift>{/* your function here! */}</Downshift>.

any | defaults to null

Pass an item or an array of items that should be selected by default.

number/null | defaults to null

This is the initial index to highlight when the menu first opens.

string | defaults to ''

This is the initial input value.

boolean | defaults to false

This is the initial isOpen value.

function(item: any) | defaults to: i => (i == null ? '' : String(i))

Used to determine the string value for the selected item (which is used to compute the inputValue.

function({/* see below */}) | default messages provided in English

This function is passed as props to a Status component nested within and allows you to create your own assertive ARIA statuses.

A default getA11yStatusMessage function is provided that will check resultCount and return "No results." or if there are results but no item is highlighted, "resultCount results are available, use up and down arrow keys to navigate." If an item is highlighted it will run itemToString(highlightedItem) and display the value of the highlightedItem.

The object you are passed to generate your status message has the following properties:

function(selectedItem: any, stateAndHelpers: object) | optional, no useful default

Called when the user selects an item. Called with the item that was selected and the new state of downshift. (see onStateChange for more info on stateAndHelpers).

• selectedItem: The item that was just selected
• stateAndHelpers: This is the exact same thing you're children prop function is called with (see Child Callback Function)

function(changes: object, stateAndHelpers: object) | optional, no useful default

This function is called anytime the internal state changes. This can be useful if you're using downshift as a "controlled" component, where you manage some or all of the state (e.g. isOpen, selectedItem, highlightedIndex, etc) and then pass it as props, rather than letting downshift control all its state itself. The parameters both take the shape of internal state ({highlightedIndex: number, inputValue: string, isOpen: boolean, selectedItem: any}) but differ slightly.

• changes: These are the properties that actually have changed since the last state change.
• stateAndHelpers: This is the exact same thing you're children prop function is called with (see Child Callback Function)

Tip: This function will be called any time any state is changed. The best way to determine whether any particular state was changed, you can use changes.hasOwnProperty('propName').

Note: the changes object will also have a type property that corresponds to a Downshift.stateChangeTypes property. This is an experimental feature so it's not recommended to use it if you can avoid it. If you need it, please open an issue to discuss solidifying the API.

number | optional, defaults the number of times you call getItemProps

This is useful if you're using some kind of virtual listing component for "windowing" (like react-virtualized).

number | control prop (read more about this in the "Control Props" section below)

The index that should be highlighted

string | control prop (read more about this in the "Control Props" section below)

The value the input should have

boolean | control prop (read more about this in the "Control Props" section below)

Whether the menu should be considered open or closed. Some aspects of the downshift component respond differently based on this value (for example, if isOpen is true when the user hits "Enter" on the input field, then the item at the highlightedIndex item is selected).

any/Array(any) | control prop (read more about this in the "Control Props" section below)

The currently selected item.

function({}) | required

This is called with an object. Read more about the properties of this object in the section "Child Callback Function"

downshift manages its own state internally and calls your onChange and onStateChange handlers with any relevant changes. The state that downshift manages includes: isOpen, selectedItem, inputValue, and highlightedIndex. Your child callback function (read more below) can be used to manipulate this state from within the render function and can likely support many of your use cases.

However, if more control is needed, you can pass any of these pieces of state as a prop (as indicated above) and that state becomes controlled. As soon as this.props[statePropKey] !== undefined, internally, downshift will determine its state based on your prop's value rather than its own internal state. You will be required to keep the state up to date (this is where onStateChange comes in really handy), but you can also control the state from anywhere, be that state from other components, redux, react-router, or anywhere else.

Note: This is very similar to how normal controlled components work elsewhere in react (like <input />). If you want to learn more about this concept, you can learn about that from this the "Controlled Components" lecture and exercises from React Training's Advanced React course.

This is where you render whatever you want to based on the state of downshift. The function is passed as the child prop: <Downshift>{/* right here*/}</Downshift>

The properties of this object can be split into three categories as indicated below:

These functions are used to apply props to the elements that you render. This gives you maximum flexibility to render what, when, and wherever you like. You call these on the element in question (for example: <input {...getInputProps()})). It's advisable to pass all your props to that function rather than applying them on the element yourself to avoid your props being overridden (or overriding the props returned). For example: getInputProps({onKeyUp(event) {console.log(event)}}).

Most of the time, you can just render a div yourself and Downshift will apply the props it needs to do its job (and you don't need to call this function). However, if you're rendering a composite component (custom component) as the root element, then you'll need to call getRootProps and apply that to your root element.

Required properties:

• refKey: if you're rendering a composite component, that component will need to accept a prop which it forwards to the root DOM element. Commonly, folks call this innerRef. So you'd call: getRootProps({refKey: 'innerRef'}) and your composite component would forward like: <div ref={props.innerRef} />

This method should be applied to the input you render. It is recommended that you pass all props as an object to this method which will compose together any of the event handlers you need to apply to the input while preserving the ones that downshift needs to apply to make the input behave.

There are no required properties for this method.

This method should be applied to the label you render. It is useful for ensuring that the for attribute on the <label> (htmlFor as a react prop) is the same as the id that appears on the input. If no htmlFor is provided then an ID will be generated and used for the input and the label for attribute.

There are no required properties for this method.

Note: You can definitely get by without using this (just provide an id to your input and the same htmlFor to your label and you'll be good with accessibility). However, we include this so you don't forget and it makes things a little nicer for you. You're welcome 😀

The props returned from calling this function should be applied to any menu items you render.

This is an impure function, so it should only be called when you will actually be applying the props to an item.

items.map(item => {
  const props = getItemProps({item}) // we're calling it here
  if (!shouldRenderItem(item)) {
    return null // but we're not using props, and downshift things we are...
  }
  return <div {...props} />
})

items
  .filter(shouldRenderItem)
  .map(item => <div {...getItemProps({item})} />)

Required properties:

• item: this is the item data that will be selected when the user selects a particular item.

Optional properties:

• index: this is how downshift keeps track of your item when updating the highlightedIndex as the user keys around. By default, downshift will assume the index is the order in which you're calling getItemProps. This is often good enough, but if you find odd behavior, try setting this explicitly. It's probably best to be explicit about index when using a windowing library like react-virtualized.

Call this and apply the returned props to a button. It allows you to toggle the Menu component. You can definitely build something like this yourself (all of the available APIs are exposed to you), but this is nice because it will also apply all of the proper ARIA attributes. The aria-label prop is in English. You should probably override this yourself so you can provide translations:

<button {...getButtonProps({
  'aria-label': translateWithId(isOpen ? 'close.menu' : 'open.menu'),
})} />

These are functions you can call to change the state of the downshift component.

otherStateToSet refers to an object to set other internal state. It is recommended to avoid abusing this, but is available if you need it.

These are values that represent the current state of the downshift component.

Examples exist on codesandbox.io:

• Bare bones autocomplete
• Multiple selection (uses controlled selectedItem API).
• Type Ahead Example (uses controlled selectedItem API).
• Integration with Apollo
• Integration with Redux
• Integration with react-instantsearch from Algolia
• Material UI (1.0.0-beta.4) Combobox Using Downshift
• Integration with GenieJS (learn more about genie here)
• Handling and displaying errors
• Integration with React Router
• Windowing with react-tiny-virtual-list
• Section/option group example
• Integration with fuzzaldrin-plus (Fuzzy matching)

If you would like to add an example, follow these steps:

1. Fork this codesandbox
2. Make sure your version (under dependencies) is the latest available version.
3. Update the title and description
4. Update the code for your example (add some form of documentation to explain what it is)
5. Add the tag: downshift:example

You'll find other examples in the stories/examples folder of the repo. And you'll find a live version of those examples here

I was heavily inspired by Ryan Florence. Watch his (free) lesson about "Compound Components". Initially downshift was a group of compound components using context to communicate. But then Jared Forsyth suggested I expose functions (the prop getters) to get props to apply to the elements rendered. That bit of inspiration made a big impact on the flexibility and simplicity of this API.

I also took a few ideas from the code in react-autocomplete and jQuery UI's Autocomplete.

You can watch me build the first iteration of downshift on YouTube:

• Part 1
• Part 2

You'll find more recordings of me working on downshift on my livestream YouTube playlist.

You can implement these other solutions using downshift, but if you'd prefer to use these out of the box solutions, then that's fine too:

• react-select
• react-autocomplete

Thanks goes to these people (emoji key):

Kent C. Dodds 💻 📖 🚇 ⚠️	Ryan Florence 🤔	Jared Forsyth 🤔 📖	Jack Moore 💡	Travis Arnold 💻 📖	Marcy Sutton 🐛 🤔	Jeremy Gayed 💡
Haroen Viaene 💡	monssef 💡	Federico Zivolo 📖	Divyendu Singh 💡	Muhammad Salman 💻	João Alberto 💻	Bernard Lin 💻 📖
Geoff Davis 💡	Anup 📖	Ferdinand Salis 🐛 💻	Kye Hohenberger 🐛	Julien Goux 🐛 💻 ⚠️	Joachim Seminck 💻	Jesse Harlin 🐛 💡
Matt Parrish 🔧	thom 💻	Vu Tran 💻	Codie Mullins 💻 💡	Mohammad Rajabifard 📖 🤔	Frank Tan 💻	Kier Borromeo 💡

This project follows the all-contributors specification. Contributions of any kind welcome!

MIT