Immutable patterns for updates in Svelte - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does 'immutable pattern' mean in Svelte updates?

It means creating a new copy of data instead of changing the original directly. This helps Svelte detect changes and update the UI efficiently.

beginner

Why should you avoid directly modifying arrays or objects in Svelte stores?

Direct modification does not trigger Svelte's reactivity because the reference stays the same. Using immutable updates by creating new arrays or objects ensures Svelte notices the change.

intermediate

How do you update an array immutably in Svelte?

Use methods like spread syntax [...array, newItem] or array methods that return new arrays (e.g., filter, map) instead of push or splice.

intermediate

Show an example of immutably updating an object in Svelte.

Use spread syntax to create a new object with updated properties:
store.update(obj => ({ ...obj, key: newValue }))

beginner

What is the benefit of using immutable patterns in Svelte's reactive updates?

It ensures Svelte can detect changes quickly and update the UI correctly without bugs or missed updates.

In Svelte, why is this update not reactive?
array.push(newItem)

A Because newItem is undefined

B Because push is not a valid JavaScript method

C Because Svelte does not support arrays

D Because push modifies the original array without changing its reference

push changes the array in place, so the reference stays the same. Svelte tracks changes by reference, so it won't detect this update.

Which method creates a new array for immutable updates in Svelte?

A push()

B filter()

C splice()

D pop()

filter() returns a new array without modifying the original, making it suitable for immutable updates.

How do you immutably update an object property in Svelte?

A obj.key = newValue

B Object.assign(obj, { key: newValue })

C store.update(obj => ({ ...obj, key: newValue }))

D delete obj.key

Using spread syntax inside store.update creates a new object with the updated property, triggering reactivity.

What happens if you directly modify a Svelte store's object without creating a new one?

A The UI will not update because the reference is unchanged

B Svelte automatically detects the change

C The app crashes

D The store resets to initial value

Svelte tracks changes by reference. Direct modification keeps the same reference, so no update is triggered.

Which is a correct immutable update for adding an item to a Svelte array store?

A store.update(arr => [...arr, newItem])

B store.update(arr => arr.push(newItem))

C store.update(arr => { arr.push(newItem); return arr; })

D store.update(arr => arr)

Using spread syntax creates a new array with the new item, triggering Svelte's reactivity.

Explain why immutable updates are important in Svelte and how you perform them for arrays and objects.

Think about how Svelte knows when data changes.

Describe a real-life example where immutable updates prevent bugs in a Svelte app.

Imagine editing a shopping list or to-do list.

Practice

1. In Svelte, why do we prefer immutable updates when changing state like arrays or objects?

easy

A. Because Svelte does not support mutable updates at all.

B. Because mutable updates are faster and recommended for performance.

C. Because immutable updates prevent any changes to the data forever.

D. Because creating new arrays or objects helps Svelte detect changes and update the UI.

Solution

1. Step 1: Understand Svelte's reactivity system

   Svelte tracks changes by comparing references of variables. If the reference changes, it knows to update the UI.

2. Step 2: Why immutable updates help

   Creating new arrays or objects changes the reference, so Svelte detects the change and updates the screen correctly.

3. Final Answer:

   Because creating new arrays or objects helps Svelte detect changes and update the UI. -> Option D

4. Quick Check:

   Immutable updates = UI updates detected [OK]

Hint: Immutable means new object/array to trigger UI update [OK]

Common Mistakes:

• Thinking mutable updates automatically update UI
• Believing Svelte forbids mutable updates
• Confusing immutability with data never changing

2. Which of the following is the correct way to immutably update an array in Svelte by adding a new item 4 to numbers?

easy

A. numbers.push(4);

B. numbers = [...numbers, 4];

C. numbers[3] = 4;

D. numbers.concat(4);

Solution

1. Step 1: Check each option for immutability

   numbers.push(4); uses push which mutates the original array. numbers[3] = 4; directly assigns an index, mutating the array. numbers.concat(4); calls concat but does not assign the result back, so no update happens.

2. Step 2: Identify the correct immutable update

   numbers = [...numbers, 4]; uses the spread operator to create a new array with the old items plus 4, then assigns it back to numbers, which is the correct immutable pattern.

3. Final Answer:

   numbers = [...numbers, 4]; -> Option B

4. Quick Check:

   Spread operator creates new array [OK]

Hint: Use spread operator and assign new array for immutable update [OK]

Common Mistakes:

• Using push which mutates original array
• Not assigning result of concat back
• Directly modifying array indexes

3. Given this Svelte code:

let todos = [
  { id: 1, text: 'Buy milk', done: false },
  { id: 2, text: 'Walk dog', done: false }
];

// Update to mark todo with id 2 as done
todos = todos.map(todo => todo.id === 2 ? { ...todo, done: true } : todo);

What will be the value of todos after this update?

medium

A. [{ id: 1, text: 'Buy milk', done: false }, { id: 2, text: 'Walk dog', done: true }]

B. [{ id: 1, text: 'Buy milk', done: true }, { id: 2, text: 'Walk dog', done: false }]

C. [{ id: 1, text: 'Buy milk', done: false }, { id: 2, text: 'Walk dog', done: false }]

D. [{ id: 1, text: 'Buy milk', done: true }, { id: 2, text: 'Walk dog', done: true }]

Solution

1. Step 1: Understand the map update logic

   The map goes through each todo. If the todo's id is 2, it creates a new object with done set to true. Otherwise, it returns the original todo unchanged.

2. Step 2: Apply the update to each todo

   Todo with id 1 remains unchanged with done: false. Todo with id 2 is updated to done: true.

3. Final Answer:

   [{ id: 1, text: 'Buy milk', done: false }, { id: 2, text: 'Walk dog', done: true }] -> Option A

4. Quick Check:

   Only todo with id 2 is marked done [OK]

Hint: map + spread updates only matching item immutably [OK]

Common Mistakes:

• Updating wrong todo item
• Mutating original todo instead of creating new
• Not returning updated todo in map

4. What is wrong with this Svelte code that tries to immutably update an object state?

let user = { name: 'Alice', age: 25 };

// Update age
user.age = 26;
user = user;

medium

A. Svelte requires a special function to update objects immutably.

B. Assigning user = user creates a new object reference, so update works fine.

C. Directly modifying user.age mutates the original object, so Svelte may not detect the change.

D. The code correctly uses immutable update patterns.

Solution

1. Step 1: Identify mutation in the code

   The line user.age = 26 directly changes the existing object, which is a mutation.

2. Step 2: Understand Svelte's change detection

   Assigning user = user does not change the reference, so Svelte does not detect any change and will not update the UI.

3. Final Answer:

   Directly modifying user.age mutates the original object, so Svelte may not detect the change. -> Option C

4. Quick Check:

   Mutating object without new reference breaks reactivity [OK]

Hint: Always create new object to update state immutably [OK]

Common Mistakes:

• Mutating object properties directly
• Assigning same object reference back
• Expecting UI to update without new object

5. You have a nested state object in Svelte:

let profile = {
  name: 'Bob',
  address: { city: 'NY', zip: '10001' }
};

// You want to update zip to '10002' immutably. Which is correct?

hard

A. profile = { ...profile, address: { ...profile.address, zip: '10002' } };

B. profile.address.zip = '10002'; profile = profile;

C. profile = { ...profile, zip: '10002' };

D. profile.address = { zip: '10002' }; profile = profile;

Solution

1. Step 1: Understand nested immutable update

   To update a nested property immutably, create new copies of each level: first the nested object, then the outer object.

2. Step 2: Analyze each option

   profile.address.zip = '10002'; profile = profile; mutates nested property directly, no new reference. profile = { ...profile, zip: '10002' }; updates zip at top level, ignoring nesting. profile.address = { zip: '10002' }; profile = profile; replaces address with incomplete object, losing city. profile = { ...profile, address: { ...profile.address, zip: '10002' } }; correctly creates new address object with updated zip, then new profile object.

3. Final Answer:

   profile = { ...profile, address: { ...profile.address, zip: '10002' } }; -> Option A

4. Quick Check:

   Nested spread creates new objects immutably [OK]

Hint: Spread nested objects to update deeply immutably [OK]

Common Mistakes:

• Mutating nested properties directly
• Not copying nested objects fully
• Losing other nested properties by overwriting