You will often want to display multiple similar components from a collection of data. You can use the JavaScript array methods to manipulate an array of data. On this page, you'll use filter() and map() with React to filter and transform your array of data into an array of components.
You will learn
How to render components from an array using JavaScript's map()
How to render only specific components using JavaScript's filter()
The only difference among those list items is their contents, their data. You will often need to show several instances of the same component using different data when building interfaces: from lists of comments to galleries of profile images. In these situations, you can store that data in JavaScript objects and arrays and use methods like map() and filter() to render lists of components from them.
Here’s a short example of how to generate a list of items from an array:
Let's say you want a way to only show people whose profession is 'chemist'. You can use JavaScript's filter() method to return just those people. This method takes an array of items, passes them through a “test” (a function that returns true or false), and returns a new array of only those items that passed the test (returned true).
You only want the items where profession is 'chemist'. The "test" function for this looks like (person) => person.profession === 'chemist'. Here's how to put it together:
Create a new array of just “chemist” people, chemists, by calling filter() on the people filtering by person.profession === 'chemist':
exportconstpeople=[{id:0,name:"Creola Katherine Johnson",profession:"mathematician",accomplishment:"spaceflight calculations",imageId:"MK3eW3A",},{id:1,name:"Mario José Molina-Pasquel Henríquez",profession:"chemist",accomplishment:"discovery of Arctic ozone hole",imageId:"mynHUSa",},{id:2,name:"Mohammad Abdus Salam",profession:"physicist",accomplishment:"electromagnetism theory",imageId:"bE7W1ji",},{id:3,name:"Percy Lavon Julian",profession:"chemist",accomplishment:"pioneering cortisone drugs, steroids and birth control pills",imageId:"IOjWm71",},{id:4,name:"Subrahmanyan Chandrasekhar",profession:"astrophysicist",accomplishment:"white dwarf star mass calculations",imageId:"lrWQx8l",},];
Arrow functions containing => { are said to have a "block body". They let you write more than a single line of code, but you have to write a return statement yourself. If you forget it, nothing gets returned!
Notice that all the sandboxes above show an error in the console:
Warning: Each child in a list should have a unique "key" prop.
You need to give each array item a key -- a string or a number that uniquely identifies it among other items in that array:
1
<likey={person.id}>...</li>
JSX elements directly inside a map() call always need keys!
Keys tell React which array item each component corresponds to, so that it can match them up later. This becomes important if your array items can move (e.g. due to sorting), get inserted, or get deleted. A well-chosen key helps React infer what exactly has happened, and make the correct updates to the DOM tree.
Rather than generating keys on the fly, you should include them in your data:
exportconstpeople=[{id:0,// Used in JSX as a keyname:"Creola Katherine Johnson",profession:"mathematician",accomplishment:"spaceflight calculations",imageId:"MK3eW3A",},{id:1,// Used in JSX as a keyname:"Mario José Molina-Pasquel Henríquez",profession:"chemist",accomplishment:"discovery of Arctic ozone hole",imageId:"mynHUSa",},{id:2,// Used in JSX as a keyname:"Mohammad Abdus Salam",profession:"physicist",accomplishment:"electromagnetism theory",imageId:"bE7W1ji",},{id:3,// Used in JSX as a keyname:"Percy Lavon Julian",profession:"chemist",accomplishment:"pioneering cortisone drugs, steroids and birth control pills",imageId:"IOjWm71",},{id:4,// Used in JSX as a keyname:"Subrahmanyan Chandrasekhar",profession:"astrophysicist",accomplishment:"white dwarf star mass calculations",imageId:"lrWQx8l",},];
Different sources of data provide different sources of keys:
Data from a database: If your data is coming from a database, you can use the database keys/IDs, which are unique by nature.
Locally generated data: If your data is generated and persisted locally (e.g. notes in a note-taking app), use an incrementing counter, crypto.randomUUID() or a package like uuid when creating items.
Imagine that files on your desktop didn't have names. Instead, you'd refer to them by their order -- the first file, the second file, and so on. You could get used to it, but once you delete a file, it would get confusing. The second file would become the first file, the third file would be the second file, and so on.
File names in a folder and JSX keys in an array serve a similar purpose. They let us uniquely identify an item between its siblings. A well-chosen key provides more information than the position within the array. Even if the position changes due to reordering, the key lets React identify the item throughout its lifetime.
You might be tempted to use an item's index in the array as its key. In fact, that's what React will use if you don't specify a key at all. But the order in which you render items will change over time if an item is inserted, deleted, or if the array gets reordered. Index as a key often leads to subtle and confusing bugs.
Similarly, do not generate keys on the fly, e.g. with key={Math.random()}. This will cause keys to never match up between renders, leading to all your components and DOM being recreated every time. Not only is this slow, but it will also lose any user input inside the list items. Instead, use a stable ID based on the data.
Note that your components won't receive key as a prop. It's only used as a hint by React itself. If your component needs an ID, you have to pass it as a separate prop: <Profile key={id} userId={id} />.
On this page you learned:
How to move data out of components and into data structures like arrays and objects.
How to generate sets of similar components with JavaScript's map().
How to create arrays of filtered items with JavaScript's filter().
Why and how to set key on each component in a collection so React can keep track of each of them even if their position or data changes.
Change it to show two separate lists one after another: Chemists and Everyone Else. Like previously, you can determine whether a person is a chemist by checking if person.profession === 'chemist'.
exportconstpeople=[{id:0,name:"Creola Katherine Johnson",profession:"mathematician",accomplishment:"spaceflight calculations",imageId:"MK3eW3A",},{id:1,name:"Mario José Molina-Pasquel Henríquez",profession:"chemist",accomplishment:"discovery of Arctic ozone hole",imageId:"mynHUSa",},{id:2,name:"Mohammad Abdus Salam",profession:"physicist",accomplishment:"electromagnetism theory",imageId:"bE7W1ji",},{id:3,name:"Percy Lavon Julian",profession:"chemist",accomplishment:"pioneering cortisone drugs, steroids and birth control pills",imageId:"IOjWm71",},{id:4,name:"Subrahmanyan Chandrasekhar",profession:"astrophysicist",accomplishment:"white dwarf star mass calculations",imageId:"lrWQx8l",},];
exportconstpeople=[{id:0,name:"Creola Katherine Johnson",profession:"mathematician",accomplishment:"spaceflight calculations",imageId:"MK3eW3A",},{id:1,name:"Mario José Molina-Pasquel Henríquez",profession:"chemist",accomplishment:"discovery of Arctic ozone hole",imageId:"mynHUSa",},{id:2,name:"Mohammad Abdus Salam",profession:"physicist",accomplishment:"electromagnetism theory",imageId:"bE7W1ji",},{id:3,name:"Percy Lavon Julian",profession:"chemist",accomplishment:"pioneering cortisone drugs, steroids and birth control pills",imageId:"IOjWm71",},{id:4,name:"Subrahmanyan Chandrasekhar",profession:"astrophysicist",accomplishment:"white dwarf star mass calculations",imageId:"lrWQx8l",},];
In this solution, the map calls are placed directly inline into the parent <ul> elements, but you could introduce variables for them if you find that more readable.
There is still a bit duplication between the rendered lists. You can go further and extract the repetitive parts into a <ListSection> component:
exportconstpeople=[{id:0,name:"Creola Katherine Johnson",profession:"mathematician",accomplishment:"spaceflight calculations",imageId:"MK3eW3A",},{id:1,name:"Mario José Molina-Pasquel Henríquez",profession:"chemist",accomplishment:"discovery of Arctic ozone hole",imageId:"mynHUSa",},{id:2,name:"Mohammad Abdus Salam",profession:"physicist",accomplishment:"electromagnetism theory",imageId:"bE7W1ji",},{id:3,name:"Percy Lavon Julian",profession:"chemist",accomplishment:"pioneering cortisone drugs, steroids and birth control pills",imageId:"IOjWm71",},{id:4,name:"Subrahmanyan Chandrasekhar",profession:"astrophysicist",accomplishment:"white dwarf star mass calculations",imageId:"lrWQx8l",},];
A very attentive reader might notice that with two filter calls, we check each person's profession twice. Checking a property is very fast, so in this example it's fine. If your logic was more expensive than that, you could replace the filter calls with a loop that manually constructs the arrays and checks each person once.
In fact, if people never change, you could move this code out of your component. From React's perspective, all that matters is that you give it an array of JSX nodes in the end. It doesn't care how you produce that array:
exportconstpeople=[{id:0,name:"Creola Katherine Johnson",profession:"mathematician",accomplishment:"spaceflight calculations",imageId:"MK3eW3A",},{id:1,name:"Mario José Molina-Pasquel Henríquez",profession:"chemist",accomplishment:"discovery of Arctic ozone hole",imageId:"mynHUSa",},{id:2,name:"Mohammad Abdus Salam",profession:"physicist",accomplishment:"electromagnetism theory",imageId:"bE7W1ji",},{id:3,name:"Percy Lavon Julian",profession:"chemist",accomplishment:"pioneering cortisone drugs, steroids and birth control pills",imageId:"IOjWm71",},{id:4,name:"Subrahmanyan Chandrasekhar",profession:"astrophysicist",accomplishment:"white dwarf star mass calculations",imageId:"lrWQx8l",},];
Each of the recipes already includes an id field, so that's what the outer loop uses for its key. There is no ID you could use to loop over ingredients. However, it's reasonable to assume that the same ingredient won't be listed twice within the same recipe, so its name can serve as a key. Alternatively, you could change the data structure to add IDs, or use index as a key (with the caveat that you can't safely reorder ingredients).
This RecipeList component contains two nested map calls. To simplify it, extract a Recipe component from it which will accept id, name, and ingredients props. Where do you place the outer key and why?
You can copy-paste the JSX from the outer map into a new Recipe component and return that JSX. Then you can change recipe.name to name, recipe.id to id, and so on, and pass them as props to the Recipe:
Here, <Recipe {...recipe} key={recipe.id} /> is a syntax shortcut saying "pass all properties of the recipe object as props to the Recipe component". You could also write each prop explicitly: <Recipe id={recipe.id} name={recipe.name} ingredients={recipe.ingredients} key={recipe.id} />.
Note that the key is specified on the <Recipe> itself rather than on the root <div> returned from Recipe. This is because this key is needed directly within the context of the surrounding array. Previously, you had an array of <div>s so each of them needed a key, but now you have an array of <Recipe>s. In other words, when you extract a component, don't forget to leave the key outside the JSX you copy and paste.
This example renders a famous haiku by Katsushika Hokusai, with each line wrapped in a <p> tag. Your job is to insert an <hr /> separator between each paragraph. Your resulting structure should look like this:
A haiku only contains three lines, but your solution should work with any number of lines. Note that <hr /> elements only appear between the <p> elements, not in the beginning or the end!
1 2 3 4 5 6 7 8 91011121314151617
constpoem={lines:["I write, erase, rewrite","Erase again, and then","A poppy blooms.",],};exportdefaultfunctionPoem(){return(<article>{poem.lines.map((line,index)=>(<pkey={index}>{line}</p>))}</article>);}
(This is a rare case where index as a key is acceptable because a poem's lines will never reorder.)
You'll either need to convert map to a manual loop, or use a fragment.
You can write a manual loop, inserting <hr /> and <p>...</p> into the output array as you go:
1 2 3 4 5 6 7 8 9101112131415161718192021
constpoem={lines:["I write, erase, rewrite","Erase again, and then","A poppy blooms.",],};exportdefaultfunctionPoem(){letoutput=[];// Fill the output arraypoem.lines.forEach((line,i)=>{output.push(<hrkey={i+"-separator"}/>);output.push(<pkey={i+"-text"}>{line}</p>);});// Remove the first <hr />output.shift();return<article>{output}</article>;}
Using the original line index as a key doesn't work anymore because each separator and paragraph are now in the same array. However, you can give each of them a distinct key using a suffix, e.g. key={i + '-text'}.
Alternatively, you could render a collection of fragments which contain <hr /> and <p>...</p>. However, the <>... shorthand syntax doesn't support passing keys, so you'd have to write <Fragment> explicitly:
1 2 3 4 5 6 7 8 910111213141516171819202122
import{Fragment}from"react";constpoem={lines:["I write, erase, rewrite","Erase again, and then","A poppy blooms.",],};exportdefaultfunctionPoem(){return(<article>{poem.lines.map((line,i)=>(<Fragmentkey={i}>{i>0&&<hr/>}<p>{line}</p></Fragment>))}</article>);}