setContext in Svelte - Step-by-Step Execution

Concept Flow - setContext

Parent Component

↓

Call setContext(key, value)

↓

Child Component

↓

Call getContext(key)

↓

Access shared value

↓

Use value in child

The parent sets a value with setContext, children get it with getContext using the same key.

Execution Sample

Svelte

import { setContext, getContext } from 'svelte';

// Parent.svelte
setContext('color', 'blue');

// Child.svelte
const color = getContext('color');

Parent shares 'color' value; child retrieves it using the same key.

Execution Table

Step	Component	Action	Key	Value Set/Get	Result
1	Parent	Call setContext	'color'	'blue'	Context 'color' set to 'blue'
2	Child	Call getContext	'color'	N/A	Retrieves 'blue' from context
3	Child	Use value	N/A	'blue'	Child uses 'blue' for rendering or logic
4	End	No more context calls	N/A	N/A	Execution stops

💡 No more context calls; child successfully accessed parent's context value

Variable Tracker

Variable	Start	After Parent setContext	After Child getContext	Final
contextMap	{}	{ 'color': 'blue' }	{ 'color': 'blue' }	{ 'color': 'blue' }
color	undefined	undefined	'blue'	'blue'

Key Moments - 2 Insights

Why does the child getContext('color') return 'blue'?

Because the parent called setContext('color', 'blue') before the child tried to get it, as shown in execution_table step 1 and 2.

What happens if the child calls getContext with a key not set by the parent?

getContext returns undefined if no matching key was set, so the child would get no value.

Visual Quiz - 3 Questions

Look at the execution table, what value does the child getContext('color') return at step 2?

A 'red'

B undefined

C 'blue'

D null

💡 Hint

Check the 'Value Set/Get' and 'Result' columns at step 2 in the execution_table.

At which step does the parent set the context value?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Action' column in execution_table to find when setContext is called.

If the parent did not call setContext, what would the child's getContext('color') return?

A undefined

B 'blue'

C null

D Error

💡 Hint

Refer to key_moments about what happens if getContext key is not set.

Concept Snapshot

setContext(key, value) shares data from parent to children.
Children use getContext(key) to access it.
Keys must match exactly.
Useful for passing data without props.
If key not set, getContext returns undefined.

Full Transcript

In Svelte, setContext lets a parent component share data with its children without passing props. The parent calls setContext with a key and value. Children call getContext with the same key to retrieve the value. This works like a hidden shared box. If the child asks for a key not set, it gets undefined. This helps keep components clean and connected. The execution table shows the parent setting 'color' to 'blue' and the child retrieving it successfully.

Practice

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

easy

A. To style components using CSS variables

B. To fetch data from an API inside a component

C. To create a reactive variable inside a component

D. To share data or functions from a parent component to its children without using props

Solution

1. Step 1: Understand the role of setContext

   setContext is used to share data or functions from a parent component to its children without passing props explicitly.

2. Step 2: Compare with other options

   Options A, B, and C describe unrelated tasks like styling, fetching data, or creating reactive variables, which are not the purpose of setContext.

3. Final Answer:

   To share data or functions from a parent component to its children without using props -> Option D

4. Quick Check:

   Sharing data without props = D [OK]

Hint: Remember: setContext shares data down without props [OK]

Common Mistakes:

• Confusing setContext with fetching data
• Thinking setContext creates reactive variables
• Mixing setContext with styling methods

2. Which of the following is the correct syntax to use setContext in a Svelte component?

easy

A. setContext('key');

B. setContext('key', value);

C. setContext(key, value);

D. setContext(value, 'key');

Solution

1. Step 1: Recall the setContext function signature

   The function takes two arguments: a unique key (usually a variable or symbol) and a value to share.

2. Step 2: Analyze the options

   setContext(key, value); correctly uses setContext(key, value); where key is a variable or symbol. setContext('key', value); uses a string literal which is discouraged because keys should be unique and not collide. setContext('key'); misses the value argument. setContext(value, 'key'); reverses the arguments.

3. Final Answer:

   setContext(key, value); -> Option C

4. Quick Check:

   Correct syntax is setContext(key, value) [OK]

Hint: Use a variable or symbol as key, then value: setContext(key, value) [OK]

Common Mistakes:

• Using string literals as keys instead of variables or symbols
• Forgetting the value argument
• Swapping key and value arguments

3. Given this parent component code:

import { setContext } from 'svelte';
const key = {};
setContext(key, 'hello');

And a child component that uses:

import { getContext } from 'svelte';
const value = getContext(key);
console.log(value);

What will be logged in the console?

medium

A. An error because key is not defined in child

B. 'hello'

C. undefined

D. null

Solution

1. Step 1: Check how key is used in parent and child

   In the parent, key is a local constant object. In the child, key is used but not imported or defined, so it is undefined in that scope.

2. Step 2: Understand the effect on getContext(key)

   Since key is not defined in the child, this causes a ReferenceError at runtime.

3. Final Answer:

   An error because key is not defined in child -> Option A

4. Quick Check:

   Undefined key in child causes error = B [OK]

Hint: Always import or define the same key in child to avoid errors [OK]

Common Mistakes:

• Assuming string keys work without importing key
• Expecting undefined instead of error
• Not realizing key must be shared or imported

4. Identify the error in this Svelte parent component code using setContext:

import { setContext } from 'svelte';
const key = Symbol();
setContext(key);

medium

A. Missing value argument in setContext call

B. Using Symbol() as key is invalid

C. setContext must be imported from 'svelte/store'

D. Key must be a string, not a Symbol

Solution

1. Step 1: Review setContext usage

   The setContext function requires two arguments: a key and a value to share.

2. Step 2: Check the code for missing arguments

   The code calls setContext(key); with only one argument, missing the value argument.

3. Final Answer:

   Missing value argument in setContext call -> Option A

4. Quick Check:

   setContext needs key and value [OK]

Hint: Always provide both key and value to setContext [OK]

Common Mistakes:

• Forgetting the value argument
• Thinking Symbol keys are invalid
• Importing setContext from wrong module

5. You want to share a function from a parent to multiple nested child components using setContext. Which approach correctly ensures all children can access the function safely?

hard

A. Use a string key like 'sharedFunc' directly in setContext and getContext calls without importing

B. Define a unique Symbol key in a separate module, import it in parent and children, then use setContext(key, func) in parent and getContext(key) in children

C. Pass the function as a prop to each child instead of using setContext

D. Define the function inside each child component separately

Solution

1. Step 1: Understand key uniqueness and sharing

   Using a unique Symbol key defined in a separate module and imported ensures the same key is used in parent and children, avoiding collisions.

2. Step 2: Compare with other options

   Use a string key like 'sharedFunc' directly in setContext and getContext calls without importing risks key collisions and is less safe. Pass the function as a prop to each child instead of using setContext works but is not using setContext. Define the function inside each child component separately duplicates code and is not sharing.

3. Final Answer:

   Define a unique Symbol key in a separate module, import it in parent and children, then use setContext(key, func) in parent and getContext(key) in children -> Option B

4. Quick Check:

   Unique shared key via module = A [OK]

Hint: Use a shared Symbol key imported by all components [OK]

Common Mistakes:

• Using string keys without sharing the key variable
• Passing functions only via props when setContext fits better
• Duplicating function code in children