Context key patterns in Svelte - Mini Project: Build & Apply

Context Key Patterns in Svelte

📖 Scenario: You are building a simple Svelte app where a parent component shares a theme color with its child components using context keys.

🎯 Goal: Learn how to create and use context keys in Svelte to pass data from a parent component to child components without props.

📋 What You'll Learn

Create a unique context key using Symbol()

Set context in the parent component using setContext

Get context in the child component using getContext

Display the shared theme color in the child component

💡 Why This Matters

🌍 Real World

Context keys let you share data like themes, user info, or settings between components without passing props through many layers.

💼 Career

Understanding context keys is important for building scalable Svelte apps where components need to share data cleanly and efficiently.

1

Create a unique context key

In a new Svelte component file, create a constant called themeKey and assign it the value Symbol('theme').

Svelte

# Your code here

Hint

Use const themeKey = Symbol('theme') to create a unique key for context.

2

Set context in the parent component

Import setContext from 'svelte'. Then use setContext(themeKey, 'darkblue') to share the theme color 'darkblue' using the themeKey.

Svelte

const themeKey = Symbol('theme');

// Import setContext and set the context with themeKey and 'darkblue'
# Your code here

Hint

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

3

Get context in the child component

In a child Svelte component, import getContext from 'svelte'. Then create a constant called theme and assign it the value returned by getContext(themeKey).

Svelte

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

setContext(themeKey, 'darkblue');

// In child component: import getContext and get theme using themeKey
# Your code here

Hint

Use getContext(themeKey) to access the shared theme value.

4

Display the theme color in the child component

In the child component's markup, add a <div> that shows the text Theme color: {theme}. This will display the shared theme color from context.

Svelte

  import { getContext } from 'svelte';
  const theme = getContext(themeKey);



# Your code here

Hint

Use a <div> with {theme} inside to show the color.

Practice

1. What is the main reason to use Symbol as a context key in Svelte?

easy

A. To ensure the key is unique and avoid conflicts between components

B. To make the key a string for easier debugging

C. To allow the key to be reused as a CSS class name

D. To automatically serialize the key for storage

Solution

1. Step 1: Understand context keys purpose

   Context keys identify data shared between components without props.

2. Step 2: Why use Symbol?

   Symbols are unique values, preventing accidental key collisions.

3. Final Answer:

   To ensure the key is unique and avoid conflicts between components -> Option A

4. Quick Check:

   Unique keys = Symbol usage [OK]

Hint: Symbols guarantee unique keys, preventing conflicts [OK]

Common Mistakes:

• Using strings that can clash with other keys
• Thinking keys must be strings for context
• Reusing keys across unrelated components

2. Which of the following is the correct way to create and export a context key in Svelte?

easy

A. export let key = new Symbol('myKey');

B. export const key = 'myKey';

C. const key = Symbol('myKey'); export default key;

D. export const key = Symbol('myKey');

Solution

1. Step 1: Check correct Symbol creation

   Symbols are created with Symbol('description'), not with new.

2. Step 2: Check export syntax

   Exporting a constant with export const key = Symbol('myKey'); is correct and common.

3. Final Answer:

   export const key = Symbol('myKey'); -> Option D

4. Quick Check:

   Correct Symbol export = export const key = Symbol('myKey'); [OK]

Hint: Use export const with Symbol() without new keyword [OK]

Common Mistakes:

• Using string instead of Symbol for key
• Using new Symbol() which is invalid
• Exporting default instead of named export

3. Given this code snippet, what will be logged in the Child.svelte component?

/* key.js */
export const userKey = Symbol('user');

/* Parent.svelte */
import { setContext } from 'svelte';
import { userKey } from './key.js';

setContext(userKey, { name: 'Alice' });

/* Child.svelte */
import { getContext } from 'svelte';
import { userKey } from './key.js';

const user = getContext(userKey);
console.log(user.name);

medium

A. Alice

B. undefined

C. Error: userKey is not defined

D. null

Solution

1. Step 1: Understand setContext and getContext usage

   Parent sets context with key userKey and value { name: 'Alice' }.

2. Step 2: Child retrieves context using same key

   Child imports userKey and calls getContext(userKey), getting the object.

3. Final Answer:

   Alice -> Option A

4. Quick Check:

   Matching keys return value = Alice [OK]

Hint: Matching Symbol keys share data correctly [OK]

Common Mistakes:

• Using different keys causing undefined
• Forgetting to import the shared key
• Expecting string keys instead of Symbol keys

4. Identify the error in this Svelte code using context keys:

/* key.js */
export const themeKey = Symbol('theme');

/* Parent.svelte */
import { setContext } from 'svelte';
import { themeKey } from './key.js';

setContext('themeKey', 'dark');

/* Child.svelte */
import { getContext } from 'svelte';
import { themeKey } from './key.js';

const theme = getContext(themeKey);
console.log(theme);

medium

A. Forgetting to import setContext in Parent

B. Using string 'themeKey' instead of Symbol key in setContext

C. Using getContext before setContext is called

D. Not exporting themeKey from key.js

Solution

1. Step 1: Check setContext key usage

   Parent uses string 'themeKey' instead of the Symbol themeKey imported from key.js.

2. Step 2: Understand key mismatch effect

   Child uses Symbol key, so getContext returns undefined because keys differ.

3. Final Answer:

   Using string 'themeKey' instead of Symbol key in setContext -> Option B

4. Quick Check:

   Key mismatch causes undefined context [OK]

Hint: Always use the same Symbol key in setContext and getContext [OK]

Common Mistakes:

• Mixing string and Symbol keys
• Assuming string keys work like Symbols
• Not importing the shared key properly

5. You want to share a theme object between multiple nested components using context keys. Which pattern is best to avoid key conflicts and ensure consistent usage?

hard

A. Create a new Symbol key in each component separately

B. Use a plain string key like 'theme' directly in setContext and getContext calls

C. Define and export a unique Symbol key in a separate file, then import it in all components

D. Use a global variable without context to share the theme

Solution

1. Step 1: Understand key uniqueness and sharing

   Using a shared Symbol key exported from one file ensures all components use the exact same key.

2. Step 2: Avoid conflicts and inconsistencies

   Using strings or separate Symbols risks conflicts or mismatches causing bugs.

3. Final Answer:

   Define and export a unique Symbol key in a separate file, then import it in all components -> Option C

4. Quick Check:

   Shared Symbol key file = consistent context [OK]

Hint: Keep keys in one file, import everywhere to avoid conflicts [OK]

Common Mistakes:

• Using different keys in different components
• Relying on strings that may clash
• Avoiding context and using globals instead