Arrays can hold any JavaScript value in them, like objects for example.

Why would this be useful?

Arrays are great ways to bundle different pieces of data about one thing.

For instance, if you are dealing with a user

you might want to know the users name, age, and birthday.

In JavaScript, you'd need three different data types to store these details,

a string, number and a date.

With objects, you can bundle these together and add labels to each piece of

data, or strings, so you can use to ask for the data later.

If you are working with users though,

you will need to be able to store many of them.

To keep track of all the user objects, you might put them into an array.

I have an array of user objects here.

You'll often see objects like this broken onto their own lines.

These just have one property.

A name property.

For a challenge, pause the video and

see if you can remove the username Samir from this array using filter.

I'll create a new variable below this one, called newUsersArray.

And I set it equal to users.filter and

then user will be the parameter.

and the user parameter to the call-back will be an object since that's what this

array contains.

We'll need to check the name property and

return false only if it hold the string "Samir",

so user.name does not equal Samir.

I'll log this to the console, And save it.

And then we'll run the file.

And it works as expected.

Now, let's add an age property to each object.

And I'll make these different ages.

Now see if you can use map to produce an array of

strings that tell how old each user is, like this.

Pause the video if you wanna work this out yourself.

Starting from the code we already have, I'll just replace filter with map.

User objects are still passed to this call-back, but

now we want to construct and return a string.

I'll use a template literal.

And I'll just copy this text as a guide.

And then I'll replace the name with a placeholder.

And we'll use user.name here.

And for the age,

we'll interpolate user.age.

Running this now.

We get the result we expected.

Now let's stretch what you've learned so far a little further.

Remember how I said you can use reduce to combine array elements into one value?

The value it returns doesn't need to be a primitive, like a string or number,

it can be an object or even another array, depending on the needs of your program.

For this challenge, see if you can use reduce to create a new object

where the user's names become properties, whose values are their ages.

I'll show you what I mean.

The new object should look like this.

So each of the user's name.

Values are the properties of this new object, and

each age is the value of that property.

And I'll just comment this out, so it doesn't interfere with the program.

Go ahead and see if you can work this out on your own.

It´s okay if you got stuck, I´ll show you how I would do this now.

Again, I´ll start with a code we already have here, replacing map with reduce.

In addition to the user object, reduce takes an accumulator parameter,

which will be the object we want to build.

I'll name it users object.

And I'll get rid of this function body here.

And I'll also want to initialize this with a new object.

And this will be passed into the usersObject each time through the array,

and we'll add the properties onto this new object.

In the body of the callback, we'll want to create a new property on usersObject.

The name property.

And we wanna set that to the age.

Like so.

I'm gonna change this variable name to the usersObject,

since that's what we're ending up with at the end of this reduce call.

And then I will also change it in my console.log.

So I will save this and run it.

And I got an error.

It says cannot set property 'Angela' of undefined.

So reduce has made it as far as the second element, before throwing this error.

And it's trying to add the property Angela onto usersObject, which is undefined.

So the reason it's undefined is.

The first time through, reduce has this initial

Object that it uses for usersObject.

And then the second time through it doesn't have anything,

because we haven't returned anything from our callback.

So just remember you always have to return a value from your callback.

And I'll put usersObject.

Save that, and down here I'll clear and run it again.

And great, we get our object with names for properties and ages for values.

Now that we've started working with objects,

let's use method chaining to apply more than one action to some arrays of data.

In the next video, we will use filter and map together.

See you there.