Why actions add reusable element behavior in Svelte - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to apply an action to an element in Svelte.

Svelte

<div use:[1]></div>

Drag options to blanks, or click blank then click option'

Aclass

BonClick

Cbind

DmyAction

Attempts:

3 left

💡 Hint

Common Mistakes

Using event handlers like 'onClick' instead of an action name.

Trying to bind or add a class instead of using an action.

In Svelte, actions are applied to elements using the use: directive followed by the action name.

2fill in blank

medium

Complete the action function to receive the element it is applied to.

Svelte

function myAction([1]) {
  // action code here
}

Drag options to blanks, or click blank then click option'

Anode

Bevent

Celement

Dtarget

Attempts:

3 left

💡 Hint

Common Mistakes

Using event or target which are not the element itself.

Using a name that does not represent the element.

The action function receives the DOM element as the first argument, commonly named node.

3fill in blank

hard

Fix the error in the action return to properly clean up when the element is removed.

Svelte

function myAction(node) {
  const handle = () => console.log('clicked');
  node.addEventListener('click', handle);
  return [1];
}

Drag options to blanks, or click blank then click option'

Anode.removeEventListener('click', handle)

B{ cleanup: () => node.removeEventListener('click', handle) }

C{ destroy: () => node.removeEventListener('click', handle) }

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Returning null or nothing, causing memory leaks.

Using a wrong method name like 'cleanup'.

The action should return an object with a destroy method to remove event listeners when the element is removed.

4fill in blank

hard

Fill both blanks to update the action when parameters change and clean up properly.

Svelte

function myAction(node, [1]) {
  function update(params) {
    console.log(params);
  }
  update([2]);
  return {
    update,
    destroy() {
      // cleanup code
    }
  };
}

Drag options to blanks, or click blank then click option'

Aparams

BinitialParams

Coptions

Dsettings

Attempts:

3 left

💡 Hint

Common Mistakes

Not naming the second argument as parameters.

Not calling update with initial parameters.

The second argument is usually named params and the initial parameters are passed to update to initialize the action.

5fill in blank

hard

Fill all three blanks to create a reusable action that adds a CSS class and removes it on destroy.

Svelte

function addClass(node, [1]) {
  node.classList.add([2]);
  return {
    destroy() {
      node.classList.[3]([2]);
    }
  };
}

Drag options to blanks, or click blank then click option'

AclassName

B'highlight'

Cremove

Dadd

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'add' instead of 'remove' in the destroy method.

Not passing the class name as a parameter.

The action takes a className parameter, adds it to the element, and removes it on destroy using remove.

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