Scoped slots are a useful feature of Vue.js that can make components more versatile and reusable. The only problem is they’re difficult to understand! Trying to get your head around the interweaving of parent and child scopes is like solving a tough math equation.

A good approach when you can’t understand something easily is to try put it to use in solving a problem. In this article, I’ll demonstrate how I used scoped slots to build a reusable list component.

Final output (Shapes and colors components))

Final output (Shapes and colors components)

You can see the finished product in this Codepen.

The Basic Component

The component we’re going to build is called my-list and it displays lists of things. The special feature is that you can customize how the list items are rendered in every usage of the component.

Let’s tackle the simplest use case first, and get my-list to render just one list of things: an array of geometric shape names and the number of sides they have.



With a bit of CSS added, that will look the following:

Example output (Shapes component)

Example output (Shapes component)
You may also like:
Building Applications With The Vue 3 Composition API.

Generalizing my-list

Now we want to make my-list versatile enough to render any kind of list. The second test case will be a list of colors, including a small swatch to show what the color looks like.

To do this, we’ll have to abstract any data specific to the shapes list. Since the items in our lists may be structured differently, we’ll give my-list a slot so the parent can define how any particular list will display.



Let’s now create two instances of the my-list component in the root instance to display our two test case lists:


That will look like this:

Example output (shapes and colors)

Example output (shapes and colors)

Superficial Components

What we’ve just created works fine, but is not great code. my-list is, by name, a component for displaying a list. But we’ve had to abstract all the logic for rendering the list into the parent. The component does little more than wrap the list with some presentational markup.

Given that there’s still repeated code in both declarations of the component (i.e. <div class="list-item" v-for="item in ...">), it’d be great if we could delegate this to the component so it isn’t so superficial.

Scoped Slots

To allow us to do this, we’ll use a scoped slot instead of a regular slot. Scoped slots allow you to pass a template to the slot instead of passing a rendered element. It’s called a “scoped” slot because although the template is rendered in the parent scope, it will have access to certain child data.

For example, a component child with a scoped slot might look like the following.

A parent that uses this component will declare a template element in the slot. This template element will have an attribute scope that names an alias object. Any props added to the slot (in the child’s template) are available as properties of the alias object.

Renders as:

Using a Scoped Slot in my-list

Let’s pass the list arrays to my-list as props. Then we can replace the slot with a scoped slot. That way my-list can be responsible for iterating the list items, but the parent can still define how each list item should display.


Now we get my-list to iterate the items. Inside the v-for loop, item is an alias to the current list item. We can create a slot and bind that list item to the slot using v-bind="item".



Note: if you haven’t seen v-bind used without an argument before, this will bind the properties of an entire object to the element. This is useful with scoped slots as often the objects you bind will have arbitrary properties which now don’t need to be specified by name.

Now we’ll return to our root instance and declare a template within the slot of my-list. Looking at the shapes list first, the template must include the scope property to which we assign an alias shape. This alias allows us to access the scoped props. Inside the template, we can use exactly the same markup we had before to display our shape list items.

Now, here’s the full template:


Although this approach has just as much markup as before, it has delegated the common functionality to the component which makes for a more robust design.

Further Reading

Source link

Write A Comment