WrappedValue and projectedValue in Swift - Step-by-Step Execution

Concept Flow - WrappedValue and projectedValue

Declare property with @propertyWrapper

↓

Access property.wrappedValue

↓

Get or set the wrapped value

↓

Access property.projectedValue

↓

Get extra info or helper from wrapper

This flow shows how a property wrapper manages a property’s value via wrappedValue and offers extra info via projectedValue.

Execution Sample

Swift

@propertyWrapper
struct Capitalized {
  private var value: String = ""
  var wrappedValue: String {
    get { value }
    set { value = newValue.capitalized }
  }
  var projectedValue: String { "Length: \(value.count)" }
}

struct Person {
  @Capitalized var name: String
  
  init(name: String) {
    self.name = name
  }
}

var p = Person(name: "john")
print(p.name)          // John
print(p.$name)         // Length: 4

This code shows a property wrapper that capitalizes a string and provides its length as projectedValue.

Execution Table

Step	Action	wrappedValue	projectedValue	Output
1	Create Person with name "john"	"John"	Length: 4
2	Access p.name (wrappedValue getter)	"John"	Length: 4	John
3	Access p.$name (projectedValue getter)	"John"	Length: 4	Length: 4
4	Set p.name = "alice"	"Alice"	Length: 5
5	Access p.name after set	"Alice"	Length: 5	Alice
6	Access p.$name after set	"Alice"	Length: 5	Length: 5
7	End of execution			Execution stops

💡 Execution stops after demonstrating wrappedValue and projectedValue access and update.

Variable Tracker

Variable	Start	After 1	After 4	Final
value (inside Capitalized)	""	"John"	"Alice"	"Alice"
wrappedValue	""	"John"	"Alice"	"Alice"
projectedValue	"Length: 0"	"Length: 4"	"Length: 5"	"Length: 5"

Key Moments - 3 Insights

Why does p.name print "John" with capital J even though we initialized with "john"?

Because the wrappedValue setter capitalizes the string before storing it, as shown in execution_table step 1 and 4.

What is p.$name and why is it different from p.name?

p.$name accesses the projectedValue, which provides extra info (string length here), shown in execution_table steps 3 and 6.

If we change p.name, does projectedValue update automatically?

Yes, projectedValue reflects the current wrappedValue state, updated after each set, as seen in steps 4 to 6.

Visual Quiz - 3 Questions

Look at the execution_table, what is the wrappedValue after step 4?

A "John"

B "alice"

C "Alice"

D "ALICE"

💡 Hint

Check the wrappedValue column at step 4 in the execution_table.

At which step does accessing projectedValue first print "Length: 4"?

A Step 2

B Step 3

C Step 1

D Step 5

💡 Hint

Look at the projectedValue column and output at step 3 in the execution_table.

If we set p.name = "bob", what would p.$name output be?

A "Length: 3"

B "Length: 4"

C "Length: 5"

D "Length: 0"

💡 Hint

Refer to variable_tracker projectedValue updates after setting wrappedValue.

Concept Snapshot

@propertyWrapper defines wrappedValue to get/set the main value.
projectedValue provides extra info accessed via $property.
Setting wrappedValue triggers custom logic (e.g., capitalization).
Accessing projectedValue gives helper data (e.g., length).
Use p.name for value, p.$name for extra info.

Full Transcript

This visual trace shows how Swift property wrappers use wrappedValue and projectedValue. The wrappedValue is the main property value, here a capitalized string. The projectedValue offers extra info, here the string length. When creating a Person with name "john", the wrappedValue setter capitalizes it to "John". Accessing p.name gets the capitalized name. Accessing p.$name gets the length string. Changing p.name updates both wrappedValue and projectedValue accordingly. This helps understand how property wrappers manage data and provide helpers.

Practice

1. What does wrappedValue represent in a Swift property wrapper?

easy

A. The main value stored or controlled by the property wrapper

B. An extra method to modify the property

C. A way to access the property's type information

D. A function to reset the property to default

Solution

1. Step 1: Understand the role of wrappedValue

   The wrappedValue is the core value that the property wrapper manages or stores internally.

2. Step 2: Differentiate from other features

   Unlike projectedValue, wrappedValue is the actual data, not extra info or behavior.

3. Final Answer:

   The main value stored or controlled by the property wrapper -> Option A

4. Quick Check:

   wrappedValue = main stored value [OK]

Hint: wrappedValue is the property's actual stored value [OK]

Common Mistakes:

• Confusing wrappedValue with projectedValue
• Thinking wrappedValue is a method
• Assuming wrappedValue holds extra metadata

2. Which syntax correctly accesses the projectedValue of a property wrapper named score?

easy

A. score.projectedValue

B. $score

C. score.$projectedValue

D. score->projectedValue

Solution

1. Step 1: Recall how to access projectedValue

   In Swift, the projectedValue is accessed using the dollar sign prefix before the property name.

2. Step 2: Match syntax to property name

   For a property named score, the projectedValue is accessed as $score.

3. Final Answer:

   $score -> Option B

4. Quick Check:

   projectedValue = $propertyName [OK]

Hint: Use $ before property name to get projectedValue [OK]

Common Mistakes:

• Trying to access projectedValue as a normal property
• Using dot syntax incorrectly
• Confusing $score with score.$projectedValue

3. Given this code, what will be printed?

 @propertyWrapper
 struct Capitalized {
     private var value: String = ""
     var wrappedValue: String {
         get { value }
         set { value = newValue.capitalized }
     }
     var projectedValue: String {
         "Length: \(value.count)"
     }
 }

 struct Person {
     @Capitalized var name: String
 }

var p = Person()
p.name = "john doe"
print(p.name)
print(p.$name)

medium

A. John Doe
Length: 8

B. john doe
Length: 8

C. John Doe
Length: 7

D. john doe
Length: 7

Solution

1. Step 1: Understand wrappedValue behavior

   Setting p.name to "john doe" triggers the setter, which capitalizes the string to "John Doe".

2. Step 2: Calculate projectedValue output

   The projectedValue returns the length of the capitalized string. "John Doe" has 8 characters including the space.

3. Final Answer:

   John Doe\nLength: 8 -> Option A

4. Quick Check:

   wrappedValue capitalizes, projectedValue shows length [OK]

Hint: wrappedValue changes value, projectedValue gives extra info [OK]

Common Mistakes:

• Counting characters without space
• Ignoring capitalization effect
• Using p.name instead of p.$name for projectedValue

4. Identify the error in this property wrapper usage:

 @propertyWrapper
 struct Trimmed {
     var wrappedValue: String {
         didSet { wrappedValue = wrappedValue.trimmingCharacters(in: .whitespaces) }
     }
 }

 struct User {
     @Trimmed var username: String
 }

var u = User()
u.username = "  alice  "
print(u.username)

medium

A. wrappedValue cannot be mutated inside didSet

B. Cannot use didSet in property wrapper

C. Missing initial value for wrappedValue

D. Property wrapper must be a class, not struct

Solution

1. Step 1: Check wrappedValue declaration

   The wrappedValue property lacks an initial value or backing storage, causing a compile error.

2. Step 2: Understand property wrapper requirements

   Property wrappers must have a stored wrappedValue or initializer to set it; here it's missing.

3. Final Answer:

   Missing initial value for wrappedValue -> Option C

4. Quick Check:

   wrappedValue needs initial value or storage [OK]

Hint: wrappedValue must have storage or initializer [OK]

Common Mistakes:

• Trying to mutate wrappedValue inside didSet
• Assuming didSet works without storage
• Confusing struct vs class requirement

5. You want to create a property wrapper that stores an integer and also tracks how many times the value was changed. Which approach correctly uses wrappedValue and projectedValue to achieve this?

hard

A. Use projectedValue only to store and access the integer

B. Use projectedValue to store the integer and wrappedValue to return the change count

C. Use wrappedValue for both storing integer and change count

D. Use wrappedValue to store the integer and projectedValue to return the change count

Solution

1. Step 1: Define roles of wrappedValue and projectedValue

   wrappedValue should hold the main integer value; projectedValue can provide extra info like change count.

2. Step 2: Match roles to requirements

   Tracking changes is extra info, so projectedValue is ideal to expose the count without mixing with main value.

3. Final Answer:

   Use wrappedValue to store the integer and projectedValue to return the change count -> Option D

4. Quick Check:

   wrappedValue = main data, projectedValue = extra info [OK]

Hint: wrappedValue stores data, projectedValue tracks extra info [OK]

Common Mistakes:

• Swapping roles of wrappedValue and projectedValue
• Trying to store multiple values in wrappedValue
• Using projectedValue as main storage