Bird
Raised Fist0
Svelteframework~10 mins

setContext in Svelte - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to set a context value in a Svelte component.

Svelte
<script>
  import { setContext } from 'svelte';
  const key = 'user';
  const user = { name: 'Alice' };
  setContext([1], user);
</script>
Drag options to blanks, or click blank then click option'
Akey
Buser
C'user'
Dcontext
Attempts:
3 left
💡 Hint
Common Mistakes
Passing the string 'user' directly instead of the variable key.
Using the value object as the key.
2fill in blank
medium

Complete the code to import the correct function for setting context in Svelte.

Svelte
<script>
  import [1] from 'svelte';
</script>
Drag options to blanks, or click blank then click option'
AgetContext
BsetContext
CcreateContext
DuseContext
Attempts:
3 left
💡 Hint
Common Mistakes
Importing getContext instead of setContext.
Using React-like function names such as useContext.
3fill in blank
hard

Fix the error in the code that tries to set context with a string key directly.

Svelte
<script>
  import { setContext } from 'svelte';
  setContext([1], { name: 'Bob' });
</script>
Drag options to blanks, or click blank then click option'
Akey
Buser
C'user'
Dcontext
Attempts:
3 left
💡 Hint
Common Mistakes
Using an undeclared variable as key.
Passing the value object as the key.
4fill in blank
hard

Fill both blanks to set context with a key and a value object.

Svelte
<script>
  import { setContext } from 'svelte';
  const [1] = 'theme';
  const [2] = { color: 'blue' };
  setContext(themeKey, themeValue);
</script>
Drag options to blanks, or click blank then click option'
AthemeKey
BthemeValue
Ctheme
Dcolor
Attempts:
3 left
💡 Hint
Common Mistakes
Using the string 'theme' as a variable name.
Mismatching variable names between declaration and usage.
5fill in blank
hard

Fill all three blanks to set context with a key, a value, and then retrieve it in a child component.

Svelte
<script>
  import { setContext, getContext } from 'svelte';
  const [1] = 'auth';
  const [2] = { loggedIn: true };
  setContext(authKey, authValue);
  const userStatus = getContext([3]);
</script>
Drag options to blanks, or click blank then click option'
AauthKey
BauthValue
Attempts:
3 left
💡 Hint
Common Mistakes
Using the value variable as the key in getContext.
Mismatching variable names between set and get.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard