Security News
RubyGems.org Adds New Maintainer Role
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
downshift
Advanced tools
A set of primitives to build simple, flexible, WAI-ARIA compliant React autocomplete components
Downshift is a React library that provides a set of primitives to build simple, flexible, WAI-ARIA compliant enhanced input React components. Its major use cases include creating customizable dropdowns, comboboxes, and autocomplete/autosuggest inputs.
Autocomplete
This code sample demonstrates how to create a basic autocomplete input using Downshift. It includes a label, an input field, and a list of suggestions that appear as the user types.
{"import Downshift from 'downshift';\n\nfunction BasicAutocomplete() {\n return (\n <Downshift\n onChange={selection => alert(selection.value)}\n itemToString={item => (item ? item.value : '')}\n >\n {({\n getInputProps,\n getItemProps,\n getLabelProps,\n getMenuProps,\n isOpen,\n inputValue,\n highlightedIndex,\n selectedItem,\n getRootProps\n }) => (\n <div {...getRootProps({}, { suppressRefError: true })}>\n <label {...getLabelProps()}>Enter a fruit</label>\n <input {...getInputProps()} />\n <ul {...getMenuProps()}>\n {isOpen\n ? items\n .filter(item => !inputValue || item.value.includes(inputValue))\n .map((item, index) => (\n <li\n {...getItemProps({\n key: item.value,\n index,\n item,\n style: {\n backgroundColor:\n highlightedIndex === index ? 'lightgray' : 'white',\n fontWeight: selectedItem === item ? 'bold' : 'normal',\n },\n })}\n >\n {item.value}\n </li>\n ))\n : null}\n </ul>\n </div>\n )}\n </Downshift>\n );\n}\n\nconst items = [{ value: 'apple' }, { value: 'pear' }, { value: 'orange' }, { value: 'grape' }, { value: 'banana' }];"}
Dropdown
This code sample shows how to create a dropdown menu using Downshift. It includes a button to toggle the dropdown and a list of selectable items.
{"import Downshift from 'downshift';\n\nfunction BasicDropdown() {\n return (\n <Downshift\n onChange={selection => alert(selection.value)}\n itemToString={item => (item ? item.value : '')}\n >\n {({\n getToggleButtonProps,\n getMenuProps,\n isOpen,\n getItemProps,\n highlightedIndex,\n selectedItem\n }) => (\n <div>\n <button {...getToggleButtonProps()}>\n {selectedItem ? selectedItem.value : 'Select an item'}\n </button>\n <ul {...getMenuProps()}>\n {isOpen\n ? items.map((item, index) => (\n <li\n {...getItemProps({\n key: item.value,\n index,\n item,\n style: {\n backgroundColor:\n highlightedIndex === index ? 'lightgray' : 'white',\n fontWeight: selectedItem === item ? 'bold' : 'normal',\n },\n })}\n >\n {item.value}\n </li>\n ))\n : null}\n </ul>\n </div>\n )}\n </Downshift>\n );\n}\n\nconst items = [{ value: 'apple' }, { value: 'pear' }, { value: 'orange' }, { value: 'grape' }, { value: 'banana' }];"}
React Select is a flexible and beautiful Select Input control for ReactJS with multiselect, autocomplete, async and creatable support. It is similar to Downshift but offers more out-of-the-box features and styles, which can be easier for quick implementations but less flexible for extensive customization.
React Autocomplete is a component for building autocomplete functionalities in React applications. It is similar to Downshift in providing a low-level API for building custom autocomplete components, but it is less feature-rich and the API is not as extensive.
Material-UI provides a set of React components that implement Google's Material Design, including an Autocomplete component. While Downshift is more of a headless utility, Material-UI's Autocomplete comes with Material Design styles and more built-in functionalities, which might be preferable for applications seeking design consistency with Material Design.
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 collection of primitive components that you can compose together to create an autocomplete component which you can reuse in your application. It's based on ideas from the talk "Compound Components" which effectively 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 causing an API that is less easy to use and 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.
This component is currently under development and is not yet released...
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@beta
This package also depends on
react
andprop-types
. Please make sure you have those installed as well.
Note also this library supports
preact
out of the box. If you are usingpreact
then look in thedist/
folder and use the module you want with thepreact
suffix.
Things are still in flux a little bit (looking for feedback).
import Downshift from 'downshift'
function BasicAutocomplete({items, onChange}) {
return (
<Downshift onChange={onChange}>
{({
getInputProps,
getItemProps,
isOpen,
inputValue,
selectedValue,
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({value: item, index})}
key={item}
style={{
backgroundColor:
highlightedIndex === index ? 'gray' : 'white',
fontWeight: selectedValue === item ? 'bold' : 'normal',
}}
>
{item}
</div>
))}
</div>
) : null}
</div>
)}
</Downshift>
)
}
function App() {
return (
<BasicAutocomplete
items={['apple', 'orange', 'carrot']}
onChange={({selectedValue}) => console.log(selectedValue)}
/>
)
}
Available components and relevant props:
This is the only component. It doesn't render anything itself, it just calls the child function and renders that. Wrap everything in this.
function(item: any)
| defaults to an identity function (i => String(i)
)
Used to determine the value
for the selected item.
any
/Array(any)
| defaults tonull
or an empty array ([]
) if themultiple
prop is true
Pass an item or an array of items that should be selected by default.
number
/null
| defaults tonull
This is the initial index to highlight when the menu first opens.
boolean
| defaults tofalse
Specifies that multiple items can be selected at once. This means that when an item is selected
it will be added to the value
array rather than replacing the existing value
.
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 getValue(highlightedItem)
and display the value of the highlightedItem
.
The object you are passed to generate your status message has the following properties:
property | type | description |
---|---|---|
getValue | function(any) | The getValue function (see props) for getting the string value from one of the options |
resultCount | number | The total items showing in the dropdown |
previousResultCount | number | The total items showing in the dropdown the last time the status was updated |
highlightedValue | any | The value of the highlighted item |
highlightedIndex | number /null | The currently highlighted index |
inputValue | string | The current input value |
isOpen | boolean | The isOpen state |
selectedValue | any | The value of the currently selected item |
function({selectedValue, previousValue})
| required
Called when the user selects an item
function({highlightedIndex, inputValue, isOpen, selectedValue})
| not required, 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, selectedValue, highlightedIndex, etc) and then pass it as props, rather than letting downshift control all its state itself.
number
| state prop (read more below)
The index that should be highlighted
string
| state prop (read more below)
The value the input should have
boolean
| state prop (read more 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).
selectedValue
any
/Array(any)
| state prop (read more below)
The currently selected value.
function({})
| required
This is called with an object with the properties listed below:
property | type | description |
---|---|---|
getRootProps | function({}) | returns the props you should apply to the root element that you render. It can be optional. Read more below |
getInputProps | function({}) | returns the props you should apply to the input element that you render. Read more below |
getLabelProps | function({}) | returns the props you should apply to the label element that you render. Read more below |
getItemProps | function({}) | returns the props you should apply to any menu item elements you render. Read more below |
getButtonProps | function({}) | returns the props you should apply to any menu toggle button element you render. Read more below |
highlightedIndex | number / null | the currently highlighted item |
setHighlightedIndex | function(index: number) | call to set a new highlighted index |
value | any / Array(any) | the currently selected item value(s) input |
inputValue | string / null | the current value of the getInputProps input |
isOpen | boolean | the menu open state |
toggleMenu | function(state: boolean) | toggle the menu open state (if state is not provided, then it will be set to the inverse of the current state) |
openMenu | function() | opens the menu |
closeMenu | function() | closes the menu |
clearSelection | function() | clears the selection |
selectItem | function(item: any) | selects the given item |
selectItemAtIndex | function(index: number) | selects the item at the given index |
selectHighlightedItem | function() | selects the item that is currently highlighted |
The functions below 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)}})
.
getRootProps
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} />
getInputProps
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.
getLabelProps
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 samehtmlFor
to yourlabel
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 😀
getItemProps
This method should be applied to any menu items you render. You pass it an object
and that object must contain index
(number) and value
(anything) properties.
Required properties:
index
: this is how downshift
keeps track of your item when
updating the highlightedIndex
as the user keys around.value
: this is the item data that will be selected when the user selects a
particular item.getButtonProps
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'),
})} />
You can pass some props which normally the downshift
will manage for you. If
you pass these props, then they become "controlled" props. In this situation,
downshift
will no longer update them directly and will instead call your
onStateChange
handler and expect you to update them. This can be useful if
you want to control the component externally (like selecting an item
from another part of the UI).
State Props are labeled above with state prop
Examples exist on codesandbox.io:
If you would like to add an example, follow these steps:
downshift:example
I was heavily inspired by Ryan Florence and his talk entitled:
"Compound Components". 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:
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:
Thanks goes to these people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
MIT
FAQs
🏎 A set of primitives to build simple, flexible, WAI-ARIA compliant React autocomplete, combobox or select dropdown components.
The npm package downshift receives a total of 582,545 weekly downloads. As such, downshift popularity was classified as popular.
We found that downshift demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.
Security News
Research
Socket's threat research team has detected five malicious npm packages targeting Roblox developers, deploying malware to steal credentials and personal data.