Why actions add reusable element behavior in Svelte - Quick Recap

Recall & Review

beginner

What is a Svelte action?

A Svelte action is a function that can be applied to an HTML element to add reusable behavior or logic directly to that element.

beginner

How do actions help with code reuse in Svelte?

Actions let you write behavior once and apply it to many elements, avoiding repeated code and making your app easier to maintain.

intermediate

What parameters does a Svelte action receive?

A Svelte action receives the HTML element it is applied to and optionally a parameter to customize its behavior.

intermediate

How does Svelte clean up actions when elements are removed?

If an action returns a function, Svelte calls it to clean up resources or event listeners when the element is removed from the DOM.

intermediate

Why is using actions better than inline event handlers for reusable behavior?

Actions separate behavior from markup, making code cleaner, easier to reuse, and easier to test compared to inline event handlers.

What does a Svelte action primarily add to an element?

A New HTML tags

B Reusable behavior or logic

C Styling and CSS classes

D Server-side rendering

Svelte actions add reusable behavior or logic to elements, not styling or HTML structure.

What argument does a Svelte action receive first?

A The event object

B The component's state

C The HTML element it is applied to

D The CSS styles

The first argument to a Svelte action is always the HTML element it is attached to.

How can a Svelte action clean up when an element is removed?

A By returning a cleanup function

B By calling a global reset method

C By removing the element manually

D By reloading the page

Returning a cleanup function from an action lets Svelte call it when the element is removed.

Why use actions instead of inline event handlers for repeated behavior?

A Actions keep code cleaner and reusable

B Inline handlers are faster

C Actions add more HTML elements

D Inline handlers support parameters better

Actions help keep code clean and reusable, unlike inline handlers which duplicate code.

Can Svelte actions accept parameters to customize behavior?

A No, parameters are not supported

B No, they only get the element

C Yes, but only as global variables

D Yes, as a second argument

Svelte actions can accept a second argument to customize their behavior.

Explain how Svelte actions help add reusable behavior to elements.

Think about how you can write one function and use it on many elements.

Describe the lifecycle of a Svelte action from applying to cleanup.

Consider what happens when the element appears and disappears.

Practice

1. What is the main purpose of actions in Svelte?

easy

A. To create new components

B. To style elements with CSS

C. To manage global state

D. To add reusable behavior directly to HTML elements

Solution

1. Step 1: Understand what actions do

   Actions in Svelte attach behavior to elements, like event listeners or animations.

2. Step 2: Compare with other options

   Creating components, managing state, or styling are done differently, not by actions.

3. Final Answer:

   To add reusable behavior directly to HTML elements -> Option D

4. Quick Check:

   Actions = reusable element behavior [OK]

Hint: Actions add behavior to elements, not components or styles [OK]

Common Mistakes:

• Confusing actions with components
• Thinking actions manage app state
• Assuming actions handle styling

2. Which is the correct syntax to use an action named tooltip on a button element in Svelte?

easy

A. Click me

B. Click me

C. Click me

D. Click me

Solution

1. Step 1: Recall Svelte action syntax

   Actions are applied with use:actionName on elements.

2. Step 2: Check each option

   Only use:tooltip matches the correct syntax; others are for events or bindings.

3. Final Answer:

   <button use:tooltip>Click me</button> -> Option A

4. Quick Check:

   Action syntax = use:actionName [OK]

Hint: Use 'use:' prefix to apply actions on elements [OK]

Common Mistakes:

• Using 'action=' instead of 'use:'
• Confusing actions with event handlers
• Trying to bind actions like variables

3. Given this Svelte action code:

function highlight(node) {
  node.style.backgroundColor = 'yellow';
  return {
    destroy() {
      node.style.backgroundColor = '';
    }
  };
}

What happens when this action is used on an element?

medium

A. The element's background turns yellow and stays yellow forever

B. The element's background turns yellow and resets when removed

C. The element's background color is set to empty string immediately

D. The element's background color changes only on hover

Solution

1. Step 1: Analyze the action behavior

   The action sets background to yellow on start, and resets it on destroy.

2. Step 2: Understand lifecycle

   Destroy runs when element is removed or action is cleaned up, resetting style.

3. Final Answer:

   The element's background turns yellow and resets when removed -> Option B

4. Quick Check:

   Action sets and cleans up style [OK]

Hint: Destroy method cleans up changes when element is removed [OK]

Common Mistakes:

• Thinking style never resets
• Assuming style changes only on hover
• Ignoring the destroy cleanup

4. Identify the issue in this Svelte action usage:

function focus(node) {
  node.focus();
}

<input use:focus />

medium

A. The action function must be async

B. The action should be called inside onMount lifecycle

C. The action should return an object with a destroy method

D. The action must be assigned to a variable before use

Solution

1. Step 1: Check action return value

   Actions should return an object with a destroy method to clean up; here it returns nothing.

2. Step 2: Understand optional return

   Returning nothing is allowed if no cleanup needed, but best practice is to return an object.

3. Final Answer:

   The action should return an object with a destroy method -> Option C

4. Quick Check:

   Actions should return cleanup object [OK]

Hint: Always return cleanup object from actions if needed [OK]

Common Mistakes:

• Thinking actions must be async
• Believing actions need lifecycle hooks
• Assuming actions must be variables

5. You want to create a reusable Svelte action that adds a tooltip to any element. Which approach best uses actions to achieve this?

hard

A. Create an action that adds event listeners to show/hide tooltip and cleans up on destroy

B. Create a component wrapping the element and tooltip inside

C. Use CSS :hover to show tooltip without JavaScript

D. Add tooltip text directly inside the element's innerHTML

Solution

1. Step 1: Understand reusable behavior with actions

   Actions attach behavior directly to elements and can manage events and cleanup.

2. Step 2: Compare options for tooltip

   Only an action adding event listeners and cleanup fits reusable behavior on any element.

3. Final Answer:

   Create an action that adds event listeners to show/hide tooltip and cleans up on destroy -> Option A

4. Quick Check:

   Actions manage reusable element behavior best [OK]

Hint: Use actions for reusable element event behavior and cleanup [OK]

Common Mistakes:

• Using components instead of actions for element behavior
• Relying only on CSS without JS for dynamic tooltips
• Modifying innerHTML directly causing side effects