Rest parameters in Svelte - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are rest parameters in Svelte?

Rest parameters allow a component to collect all extra props passed to it into a single object. This helps to pass down or handle unknown or additional attributes easily.

beginner

How do you declare rest parameters in a Svelte component?

You use the $$restProps variable inside the component script. It automatically contains all props not explicitly declared.

intermediate

Why use rest parameters instead of declaring all props explicitly?

Rest parameters let you handle extra or unknown props without listing them all. This is useful for forwarding attributes like <code>class</code>, <code>id</code>, or event handlers.

beginner

How can you apply rest parameters to an HTML element inside a Svelte component?

You spread $$restProps on the element using {...$$restProps}. This passes all extra props to that element.

intermediate

What happens if you pass a prop to a Svelte component that is not declared and you do not use rest parameters?

The extra prop is ignored and not accessible inside the component. Using $$restProps lets you capture those props.

In Svelte, which variable holds all extra props passed to a component?

A props

B $$extraProps

C restParams

D $$restProps

The special variable $$restProps contains all props not explicitly declared in the component.

How do you pass all extra props to an HTML element inside a Svelte component?

A {...$$restProps}

B {...attributes}

C {...extra}

D {...props}

You spread $$restProps on the element like {...$$restProps} to forward all extra props.

What is a common use case for rest parameters in Svelte components?

A To declare all props explicitly

B To collect and forward unknown props

C To prevent passing props

D To handle events only

Rest parameters help collect unknown or extra props so you can forward or handle them flexibly.

If a prop is not declared and $$restProps is not used, what happens to that prop?

A It is ignored inside the component

B It is accessible normally

C It causes an error

D It is automatically forwarded

Props not declared and not captured by $$restProps are ignored inside the component.

Which of these is NOT true about $$restProps in Svelte?

A It is reactive

B It contains all undeclared props

C It must be declared manually

D It can be spread on elements

$$restProps is a built-in variable and does not need manual declaration.

Explain how rest parameters work in Svelte components and why they are useful.

Think about how you can pass extra HTML attributes without declaring each one.

Describe how to use $$restProps to forward all extra props to a button element inside a Svelte component.

Remember the spread syntax inside the element tag.

Practice

1. In Svelte, what does the rest parameter syntax ...props inside a component's export let statement do?

easy

A. It creates a new event handler for all properties.

B. It limits the component to accept only one property named props.

C. It collects all extra passed properties into an object called props.

D. It automatically binds all properties to the component's state.

Solution

1. Step 1: Understand rest parameters in Svelte

   Rest parameters collect all extra properties passed to a component that are not explicitly declared.

2. Step 2: Analyze the syntax export let ...props

   This syntax gathers all remaining props into an object named props, allowing flexible access.

3. Final Answer:

   It collects all extra passed properties into an object called props. -> Option C

4. Quick Check:

   Rest parameters = collect extra props [OK]

Hint: Rest parameters gather extra inputs into one object [OK]

Common Mistakes:

• Thinking rest parameters limit props instead of collecting them
• Confusing rest parameters with event handlers
• Assuming rest parameters auto-bind to state

2. Which of the following is the correct way to declare a rest parameter to collect extra props in a Svelte component?

easy

A. export let ...restProps;

B. export let restProps = ...;

C. export let ...restProps = {};

D. export let restProps...;

Solution

1. Step 1: Recall correct rest parameter syntax in Svelte

   Rest parameters use the spread operator ... before the variable name in export let.

2. Step 2: Check each option's syntax

   export let ...restProps; correctly uses export let ...restProps;. Options A, C, and D misuse assignment or spread placement.

3. Final Answer:

   export let ...restProps; -> Option A

4. Quick Check:

   Rest parameter syntax = export let ...name; [OK]

Hint: Rest parameters use ... before variable name without assignment [OK]

Common Mistakes:

• Adding assignment (=) with rest parameters
• Placing ... after variable name
• Using invalid syntax like ...restProps = {}

3. Given this Svelte component code:

  <script>
    export let name;
    export let ...restProps;
  </script>

  <h1>Hello {name}!</h1>
  <pre>{JSON.stringify(restProps)}</pre>

And this usage:

<MyComponent name="Anna" age={30} city="NY" />

What will be rendered inside the <pre> tag?

medium

A. {"age":30,"city":"NY"}

B. {"name":"Anna"}

C. {"name":"Anna","age":30,"city":"NY"}

D. SyntaxError

Solution

1. Step 1: Understand restProps collects extra props

   The declared prop name is separate; restProps collects all other props like age and city.

2. Step 2: Check what JSON.stringify(restProps) outputs

   It outputs an object with keys age and city and their values.

3. Final Answer:

   {"age":30,"city":"NY"} -> Option A

4. Quick Check:

   Rest props exclude declared props [OK]

Hint: Rest props exclude declared props, collect the rest [OK]

Common Mistakes:

• Including declared props inside restProps
• Expecting all props in restProps
• Confusing restProps with a syntax error

4. Consider this Svelte component snippet:

<script>
  export let ...props;
  console.log(props);
</script>

When you try to compile this, what error will you get?

medium

A. TypeError: Cannot use rest parameter here

B. No error, props logs correctly

C. ReferenceError: props is not defined

D. SyntaxError: Rest parameter must be last in export list

Solution

1. Step 1: Check rest parameter rules in Svelte

   Rest parameters must be the last in the export list and cannot be declared alone if other exports exist.

2. Step 2: Analyze the code snippet

   The snippet uses only one rest parameter export, which is valid. However, Svelte currently does not support rest parameters alone in export let statements; this causes a syntax error.

3. Final Answer:

   SyntaxError: Rest parameter must be last in export list -> Option D

4. Quick Check:

   Rest parameters have strict placement rules [OK]

Hint: Rest parameters must be last and cannot be alone in export list [OK]

Common Mistakes:

• Thinking rest parameters require other exports first
• Expecting syntax error on valid single rest declaration
• Confusing rules for multiple exports with single case

5. You want to create a Svelte component that accepts any number of extra HTML attributes and applies them to a <button> element. Which code correctly uses rest parameters to achieve this?

hard

A. <script>
export let ...attrs;
</script>

<button {...attrs}>Click me</button>

B. <script>
export let attrs = {};
</script>

<button {...attrs}>Click me</button>

C. <script>
export let ...attrs = {};
</script>

<button {...attrs}>Click me</button>

D. <script>
export let attrs;
</script>

<button {...attrs}>Click me</button>

Solution

1. Step 1: Understand Svelte's handling of extra HTML attributes

   Svelte does not currently support rest parameters in export let to collect arbitrary extra HTML attributes.

2. Step 2: Use a single prop with default empty object

   Declaring export let attrs = {}; and spreading {...attrs} on the button is the correct way to accept and apply extra attributes.

3. Final Answer:

   export let attrs = {}; with <button {...attrs}> -> Option B

4. Quick Check:

   Use a single prop object for extra attributes [OK]

Hint: Use a single prop object and spread it on element [OK]

Common Mistakes:

• Assigning default empty object to rest parameter
• Not using rest parameter syntax for extra props
• Passing undefined attrs without rest parameter