Bird
Raised Fist0
Svelteframework~30 mins

getContext in Svelte - Mini Project: Build & Apply

Choose your learning style10 modes available
Sharing Data Between Svelte Components Using getContext
📖 Scenario: You are building a simple Svelte app where a parent component shares a message with its child component without passing props directly.
🎯 Goal: Learn how to use setContext in a parent component and getContext in a child component to share data.
📋 What You'll Learn
Create a parent component that sets a context value
Create a child component that gets the context value
Display the shared message inside the child component
Use Svelte's setContext and getContext functions correctly
💡 Why This Matters
🌍 Real World
Sharing data between components without passing props directly is common in Svelte apps for cleaner and simpler code.
💼 Career
Understanding getContext and setContext helps in building scalable Svelte applications and working with component communication patterns used in professional projects.
Progress0 / 4 steps
1
Create the Parent Component with a Message
Create a Svelte component called Parent.svelte. Inside its <script> tag, declare a variable called message and set it to the string "Hello from Parent".
Svelte
Hint

Use let message = "Hello from Parent"; inside the <script> tag.

2
Set the Context in the Parent Component
In Parent.svelte, import setContext from "svelte". Then call setContext with the key "sharedMessage" and the value message.
Svelte
Hint

Remember to import setContext and call it with the key and message.

3
Create the Child Component to Get the Context
Create a new Svelte component called Child.svelte. Inside its <script> tag, import getContext from "svelte". Use getContext with the key "sharedMessage" to get the message and store it in a variable called receivedMessage.
Svelte
Hint

Use getContext("sharedMessage") and assign it to receivedMessage.

4
Display the Shared Message in the Child Component
In Child.svelte, below the paragraph, add a new paragraph that displays the variable receivedMessage using Svelte's curly braces syntax.
Svelte
Hint

Use {receivedMessage} inside a paragraph to show the message.

Practice

(1/5)
1. What is the main purpose of getContext in Svelte?
easy
A. To access data provided by a parent component without passing props
B. To create a new reactive variable inside a component
C. To define a component's local state
D. To listen for DOM events inside a component

Solution

  1. Step 1: Understand the role of getContext

    getContext is used to access data that a parent component has shared using setContext.

  2. Step 2: Compare with other options

    Other options describe unrelated tasks like local state or event listening, which getContext does not do.

  3. Final Answer:

    To access data provided by a parent component without passing props -> Option A
  4. Quick Check:

    getContext accesses parent data = B [OK]
Hint: Remember: getContext reads shared parent data [OK]
Common Mistakes:
  • Confusing getContext with local state creation
  • Thinking getContext listens to events
  • Assuming getContext sets data instead of getting
2. Which of the following is the correct syntax to retrieve a context value with key 'user' in a Svelte component?
easy
A. const user = getContext({ key: 'user' });
B. const user = getContext('user');
C. const user = getContext(user);
D. const user = setContext('user');

Solution

  1. Step 1: Recall getContext syntax

    getContext takes a string key to retrieve the shared value.

  2. Step 2: Analyze options

    const user = getContext('user'); uses the correct string key syntax. const user = setContext('user'); wrongly uses setContext. const user = getContext(user); passes a variable instead of a string. const user = getContext({ key: 'user' }); passes an object, which is invalid.

  3. Final Answer:

    const user = getContext('user'); -> Option B
  4. Quick Check:

    getContext('key') syntax = D [OK]
Hint: Use string keys in quotes with getContext [OK]
Common Mistakes:
  • Using setContext instead of getContext
  • Passing variables or objects instead of string keys
  • Missing quotes around the key
3. Given the parent component sets context with setContext('theme', 'dark'), what will the child component log with console.log(getContext('theme'))?
medium
A. 'dark'
B. 'light'
C. undefined
D. null

Solution

  1. Step 1: Understand setContext and getContext relation

    The parent sets the key 'theme' with value 'dark'. The child uses getContext with the same key.

  2. Step 2: Determine the logged value

    Since the keys match, getContext returns 'dark'. Other options are incorrect values or undefined.

  3. Final Answer:

    'dark' -> Option A
  4. Quick Check:

    Matching keys return set value = A [OK]
Hint: Matching keys return parent's setContext value [OK]
Common Mistakes:
  • Expecting default or unrelated values
  • Using different keys causing undefined
  • Confusing setContext and getContext roles
4. What is the error in this child component code snippet?
const data = getContext();
medium
A. getContext must be imported from 'svelte/store'
B. getContext cannot be used in child components
C. getContext requires two arguments
D. Missing key argument in getContext call

Solution

  1. Step 1: Check getContext usage

    getContext requires a key argument to specify which context to retrieve.

  2. Step 2: Evaluate the code snippet

    The snippet calls getContext without any argument, causing an error.

  3. Final Answer:

    Missing key argument in getContext call -> Option D
  4. Quick Check:

    getContext needs a key argument = A [OK]
Hint: Always pass a key string to getContext [OK]
Common Mistakes:
  • Calling getContext without arguments
  • Thinking getContext needs two arguments
  • Importing getContext from wrong module
5. In a nested component structure, if a grandchild calls getContext('settings') but only the grandparent used setContext('settings', {mode: 'auto'}), what will the grandchild receive?
hard
A. An error because only the direct parent can provide context
B. undefined because context is not passed through intermediate components
C. The object {mode: 'auto'} from the grandparent
D. An empty object {} because context resets at each level

Solution

  1. Step 1: Understand context propagation in Svelte

    Context set by any ancestor is accessible by all descendants, not just direct children.

  2. Step 2: Apply to the nested structure

    The grandchild can access the 'settings' context set by the grandparent, receiving the object {mode: 'auto'}.

  3. Final Answer:

    The object {mode: 'auto'} from the grandparent -> Option C
  4. Quick Check:

    Context flows down all descendants = C [OK]
Hint: Context flows down all descendants, not just direct children [OK]
Common Mistakes:
  • Thinking only direct parent context is accessible
  • Expecting undefined if intermediate components don't set context
  • Assuming context resets at each component level
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