Send an Emit Event with Data From a Vue Component to It's Parent

Share this video with your friends

Social Share Links

Send Tweet
Published 3 years ago
Updated a year ago

We'll see how we can define our own events that our components can emit to their parents. We'll also see how the parent can respond to these events using the v-on or @ directive, just like any other event.

Instructor: [0:00] So far, we have created these components for bronze, silver, and gold that we can set some tickets and we can add tickets.

[0:11] It changes the internal state of the component, but so far does nothing to the external state. It's not updating the tickets up here, and it's not updating what the route understands about how many tickets are left. To be able to do that, we need to add some custom events to our component.

[0:31] When we click our button to add tickets, we want our component to tell the parent that something has happened. We use the this.emit helper to emit a custom event, and we can name this whatever we like. We can define these in camelCase or in kebab-case. Let's emit the event, buyTickets.

[0:58] If I go to buy two tickets, I'm clicking over here to the timeline. If I buy a ticket, you can see this component event has been emitted.

[1:10] Back in our component, we want to create an v-on or an @ to our component, buy tickets. We want to invoke a method when that happens. Let's just call it buyTickets for now. If we go back to main.js and define buyTickets, let's just console.log(Buy some tickets.). Let's check if that works OK. Buy some tickets.

[1:46] That's all well and good, but I would like some more information for my event. I would like to know, when I'm buying tickets, how many tickets to buy and what type of ticket I want to buy. I want to send some values. Let's send this.tickets toBuy and this.name. We're listing to buyTickets and we're triggering this function when that happens.

[2:15] The order that we parse them out is the order we can expect them. Number of tickets and name. Let's console.log that. Let's buy that number of that type of ticket. Check that's working OK, buy two bronze, hopefully, buy eight silver, buy 28 gold.

[2:51] We've got that event. Now, I would like to update the cart. If I update cart here, we can see we're updating by the number. We could, at this point, just this.cart is going to equal this.cart plus the number of tickets. If I buy two tickets, buy another three tickets, then I have five tickets.

[3:17] But we're losing the context. We don't know how many of each ticket we have. We might want to change updateCart to deal with that.

egghead
egghead
~ 30 minutes ago

Member comments are a way for members to communicate, interact, and ask questions about a lesson.

The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io

Be on-Topic

Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.

Avoid meta-discussion

  • This was great!
  • This was horrible!
  • I didn't like this because it didn't match my skill level.
  • +1 It will likely be deleted as spam.

Code Problems?

Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context

Details and Context

Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!

Markdown supported.
Become a member to join the discussionEnroll Today