Event forwarding in Svelte - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is event forwarding in Svelte?

Event forwarding in Svelte means passing an event from a child component up to its parent without manually re-dispatching it. It lets the parent listen directly to events fired inside the child.

intermediate

How do you forward all events from a child component in Svelte?

Use {...$$restProps} to forward events and props automatically to the parent component.

beginner

Why is event forwarding useful in component design?

It simplifies communication by avoiding extra code to catch and re-emit events. This keeps components clean and lets parents handle events directly.

intermediate

Which Svelte feature helps to forward events without writing extra code?

The $$restProps object automatically forwards unknown props and events to the parent, enabling event forwarding with minimal code.

beginner

What happens if you don’t forward an event from a child component?

The parent component won’t hear the event. You must either forward it or re-dispatch it manually for the parent to respond.

In Svelte, how can a parent component listen to a child's event without extra code?

A By writing a callback in the child

B By importing the child's script

C By using global variables

D By using event forwarding

Event forwarding lets the parent listen directly to events from the child without extra code.

Which Svelte syntax helps forward all events from a child component?

A {...$$restProps}

B <script context='module'>

C <svelte:window>

D <slot>

{...$$restProps} enables forwarding all events from the child.

What is the role of $$restProps in event forwarding?

A It styles the component

B It blocks events from bubbling

C It forwards unknown props and events to the parent

D It imports external scripts

$$restProps forwards unknown props and events, enabling event forwarding.

If a child component fires a custom event but does not forward it, what happens?

A The event is logged in console

B The parent cannot listen to it

C The event is automatically forwarded

D The event triggers a page reload

Without forwarding, the parent does not receive the child's event.

Why might you want to forward events instead of re-dispatching them manually?

A To reduce extra code and keep components simple

B To prevent events from firing

C To change event names automatically

D To block parent components from listening

Forwarding reduces boilerplate and keeps components clean.

Explain event forwarding in Svelte and why it is helpful.

Think about how parents listen to child events easily.

Describe how you can implement event forwarding in a Svelte component.

Focus on Svelte syntax that helps forward events automatically.

Practice

1. What does event forwarding in Svelte primarily help with?

easy

A. Passing events from a child component to its parent component easily

B. Automatically styling components based on events

C. Preventing events from bubbling up the DOM tree

D. Creating new custom events inside a component

Solution

1. Step 1: Understand event forwarding concept

   Event forwarding allows a child component to send events directly to its parent without extra code inside the child.

2. Step 2: Identify the main purpose

   This simplifies communication by letting the parent listen to child events as if they came from the parent itself.

3. Final Answer:

   Passing events from a child component to its parent component easily -> Option A

4. Quick Check:

   Event forwarding = passing events up [OK]

Hint: Event forwarding means child events reach parent directly [OK]

Common Mistakes:

• Thinking it styles components
• Confusing with event stopping
• Assuming it creates new events

2. Which syntax correctly forwards a click event from a child component <Child /> to its parent in Svelte?

easy

A. <Child forward:click />

B. <Child bind:click />

C. <Child on:click />

D. <Child use:click />

Solution

1. Step 1: Recall event forwarding syntax

   In Svelte, forwarding an event means listening on the child component tag with on:eventName.

2. Step 2: Match correct syntax

   The correct syntax to listen and forward a click event is <Child on:click />. Other options are invalid or unrelated.

3. Final Answer:

   <Child on:click /> -> Option C

4. Quick Check:

   Use on:eventName to forward events [OK]

Hint: Use on:eventName on child tag to forward events [OK]

Common Mistakes:

• Using bind:click which is for two-way binding
• Using forward:click which is not valid syntax
• Using use:click which is for actions

3. Given this Svelte code:

<!-- Parent.svelte -->
<Child on:customEvent={handleEvent} />

<script>
  function handleEvent(e) {
    console.log(e.detail);
  }
</script>

<!-- Child.svelte -->
<script>
  import { createEventDispatcher } from 'svelte';
  const dispatch = createEventDispatcher();
  function send() {
    dispatch('customEvent', 'hello');
  }
</script>

<button on:click={send}>Send</button>

What will be logged when the button is clicked?

medium

A. undefined

B. Nothing is logged

C. An error occurs

D. "hello"

Solution

1. Step 1: Understand event dispatching in Child

   The child dispatches a 'customEvent' with detail 'hello' when the button is clicked.

2. Step 2: Check event forwarding and handling in Parent

   The parent listens to on:customEvent on the child and calls handleEvent, which logs e.detail.

3. Final Answer:

   "hello" -> Option D

4. Quick Check:

   Dispatched event detail logs "hello" [OK]

Hint: Dispatched event detail appears in handler e.detail [OK]

Common Mistakes:

• Expecting event object instead of detail
• Thinking event is not forwarded automatically
• Assuming no log happens without explicit forwarding

4. What is wrong with this Svelte code if the parent does not receive the child's submit event?

<!-- Parent.svelte -->
<Child on:submit={handleSubmit} />

<script>
  function handleSubmit() {
    alert('Submitted');
  }
</script>

<!-- Child.svelte -->
<script>
  import { createEventDispatcher } from 'svelte';
  const dispatch = createEventDispatcher();
  function submit() {
    dispatch('submit');
  }
</script>

<button on:click={submit}>Submit</button>

medium

A. The parent must use bind:submit instead of on:submit

B. The child event name 'submit' conflicts with native DOM event and needs renaming

C. The dispatch function is not called correctly

D. The parent forgot to import Child component

Solution

1. Step 1: Identify event name conflict

   The child dispatches an event named 'submit', which is a native DOM event on buttons and forms.

2. Step 2: Understand event forwarding conflict

   Because 'submit' is native, the parent's on:submit may listen to the native event, not the child's custom event, causing confusion.

3. Final Answer:

   The child event name 'submit' conflicts with native DOM event and needs renaming -> Option B

4. Quick Check:

   Custom event name conflicts cause forwarding issues [OK]

Hint: Avoid native event names for custom events [OK]

Common Mistakes:

• Assuming dispatch is incorrect
• Thinking parent must bind instead of on
• Ignoring native event name conflicts

5. You have a nested component structure: Grandparent > Parent > Child. The Child dispatches a save event. How can you forward this event so the Grandparent can listen to it directly without adding handlers in Parent?

hard

A. In Parent, listen to save and re-dispatch it with createEventDispatcher

B. In Parent, forward the save event by adding <Child on:save /> and export let $$restProps with <slot {...$$restProps} />

C. In Grandparent, import Child directly and listen to save

D. In Child, dispatch save with option

Solution

1. Step 1: Understand event forwarding through intermediate components

   Events do not automatically bubble through multiple Svelte components; Parent must forward Child's event.

2. Step 2: Forward event in Parent by listening and re-dispatching

   Parent listens to save on Child and uses createEventDispatcher to dispatch the same event upward.

3. Final Answer:

   In Parent, listen to save and re-dispatch it with createEventDispatcher -> Option A

4. Quick Check:

   Intermediate component must re-dispatch events [OK]

Hint: Intermediate must re-dispatch events to forward [OK]

Common Mistakes:

• Assuming events bubble automatically through components
• Trying to listen in grandparent without parent forwarding
• Misusing slot props for event forwarding