Why property wrappers reduce boilerplate in Swift - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a property wrapper named Capitalized.

Swift

propertyWrapper struct Capitalized {
    private var value: String = ""
    var wrappedValue: String {
        get { value }
        set { value = newValue[1] }
    }
}

Drag options to blanks, or click blank then click option'

A.lowercased()

B.capitalized

C.uppercased()

D.trimmingCharacters(in: .whitespaces)

Attempts:

3 left

💡 Hint

Common Mistakes

Using a method that changes case incorrectly, like lowercased or uppercased.

Forgetting to apply the method to the newValue.

The property wrapper modifies the new value by applying the capitalized method to reduce repetitive capitalization code.

2fill in blank

medium

Complete the code to apply the Capitalized property wrapper to the name property.

Swift

struct Person {
    @[1] var name: String
}

Drag options to blanks, or click blank then click option'

ALowercased

BTrimmed

CCapitalized

DUppercased

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong wrapper name or forgetting the '@' symbol.

Confusing capitalization with other string transformations.

The @Capitalized wrapper is applied to the name property to automatically capitalize it.

3fill in blank

hard

Fix the error in the property wrapper by completing the missing initializer.

Swift

propertyWrapper struct Capitalized {
    private var value: String = ""
    var wrappedValue: String {
        get { value }
        set { value = newValue.capitalized }
    }
    init([1]) {
        self.wrappedValue = wrappedValue
    }
}

Drag options to blanks, or click blank then click option'

AwrappedValue: String

Bvalue: String

CnewValue: String

DinitialValue: String

Attempts:

3 left

💡 Hint

Common Mistakes

Using a parameter name other than wrappedValue.

Not initializing the property wrapper's value properly.

The initializer must accept wrappedValue to initialize the property wrapper correctly.

4fill in blank

hard

Fill both blanks to create a property wrapper that trims whitespace and capitalizes the string.

Swift

propertyWrapper struct TrimmedCapitalized {
    private var value: String = ""
    var wrappedValue: String {
        get { value }
        set { value = newValue[1][2] }
    }
}

Drag options to blanks, or click blank then click option'

A.trimmingCharacters(in: .whitespaces)

B.capitalized

C.lowercased()

D.uppercased()

Attempts:

3 left

💡 Hint

Common Mistakes

Reversing the order of trimming and capitalization.

Using incorrect string methods.

First trim whitespace, then capitalize the string to reduce repetitive code.

5fill in blank

hard

Fill all three blanks to create a property wrapper that trims, capitalizes, and limits the string length to 10 characters.

Swift

propertyWrapper struct TrimCapLimit {
    private var value: String = ""
    var wrappedValue: String {
        get { value }
        set {
            let trimmed = newValue[1]
            let capitalized = trimmed[2]
            value = String(capitalized.prefix([3]))
        }
    }
}

Drag options to blanks, or click blank then click option'

A.trimmingCharacters(in: .whitespaces)

B.capitalized

C10

D.lowercased()

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong order of string methods.

Forgetting to convert prefix result back to String.

Using an incorrect limit number.

The code trims whitespace, capitalizes the string, and then limits it to 10 characters to reduce repetitive code.

Practice

1. What is the main reason property wrappers reduce boilerplate code in Swift?

easy

A. They replace functions with variables

B. They allow properties to be declared without types

C. They automatically generate UI elements for properties

D. They encapsulate common property logic to reuse it easily

Solution

1. Step 1: Understand property wrappers purpose

   Property wrappers let you write common property behavior once and reuse it.

2. Step 2: Identify how boilerplate is reduced

   By wrapping repeated code for properties, you avoid rewriting the same logic multiple times.

3. Final Answer:

   They encapsulate common property logic to reuse it easily -> Option D

4. Quick Check:

   Property wrappers = reuse common logic [OK]

Hint: Think: property wrappers wrap repeated code [OK]

Common Mistakes:

• Confusing property wrappers with UI features
• Thinking property wrappers remove type declarations
• Believing property wrappers replace functions

2. Which of the following is the correct syntax to declare a property wrapper in Swift?

easy

A. @propertyWrapper struct Wrapper { var wrappedValue: Int }

B. propertyWrapper struct Wrapper { var wrappedValue: Int }

C. @wrapper struct Wrapper { var wrappedValue: Int }

D. @propertyWrapper class Wrapper { wrappedValue: Int }

Solution

1. Step 1: Recall property wrapper declaration syntax

   Property wrappers use the attribute @propertyWrapper before a struct or class.

2. Step 2: Check the correct syntax details

   @propertyWrapper struct Wrapper { var wrappedValue: Int } correctly uses @propertyWrapper and defines wrappedValue with a type and var keyword.

3. Final Answer:

   @propertyWrapper struct Wrapper { var wrappedValue: Int } -> Option A

4. Quick Check:

   @propertyWrapper + struct + wrappedValue = correct syntax [OK]

Hint: Remember: @propertyWrapper before struct/class [OK]

Common Mistakes:

• Omitting the @ symbol before propertyWrapper
• Using wrong attribute name like @wrapper
• Missing var keyword for wrappedValue

3. Consider this Swift code using a property wrapper:

@propertyWrapper
struct Clamped {
    var value: Int
    var wrappedValue: Int {
        get { value }
        set { value = min(max(newValue, 0), 10) }
    }
    init(wrappedValue: Int) {
        self.value = min(max(wrappedValue, 0), 10)
    }
}

struct Score {
    @Clamped var points: Int
}

var s = Score(points: 15)
print(s.points)

What is the output?

medium

A. 15

B. 0

C. 10

D. Compilation error

Solution

1. Step 1: Understand the Clamped property wrapper behavior

   The wrapper limits values between 0 and 10 using min and max functions.

2. Step 2: Analyze initialization and print output

   When Score is created with points = 15, the wrapper clamps it to 10. Printing s.points outputs 10.

3. Final Answer:

   10 -> Option C

4. Quick Check:

   Clamped value of 15 = 10 [OK]

Hint: Check how wrappedValue clamps values [OK]

Common Mistakes:

• Assuming original value 15 is stored without clamping
• Confusing wrappedValue with value property
• Expecting runtime error for out-of-range value

4. This Swift code uses a property wrapper but causes a compile error. What is the mistake?

@propertyWrapper
struct Capitalized {
    var wrappedValue: String {
        didSet { wrappedValue = wrappedValue.capitalized }
    }
    init(wrappedValue: String) {
        self.wrappedValue = wrappedValue.capitalized
    }
}

struct Person {
    @Capitalized var name: String
}

medium

A. Using didSet inside wrappedValue causes infinite recursion

B. Missing var keyword for wrappedValue property

C. Property wrapper must be a class, not struct

D. Initializer should not modify wrappedValue

Solution

1. Step 1: Identify the problem with didSet on wrappedValue

   Using didSet on wrappedValue that modifies wrappedValue causes infinite recursion.

2. Step 2: Understand why this causes compile error

   The setter triggers didSet, which sets wrappedValue again, looping endlessly and causing error.

3. Final Answer:

   Using didSet inside wrappedValue causes infinite recursion -> Option A

4. Quick Check:

   didSet modifying wrappedValue = recursion error [OK]

Hint: Avoid modifying wrappedValue inside didSet [OK]

Common Mistakes:

• Thinking struct cannot be property wrapper
• Ignoring recursion caused by didSet setter
• Believing initializer causes error here

5. You want to create a property wrapper that logs every time a property changes without repeating logging code in every setter. Which approach best uses property wrappers to reduce boilerplate?

hard

A. Use a global function to log changes and call it in setters

B. Create a @Logger wrapper that prints old and new values inside wrappedValue's setter

C. Add print statements manually in every property setter

D. Override Swift's default setter behavior globally

Solution

1. Step 1: Identify how property wrappers reduce repeated code

   Property wrappers let you write logging once inside the wrapper's setter.

2. Step 2: Compare options for logging property changes

   Create a @Logger wrapper that prints old and new values inside wrappedValue's setter uses a @Logger wrapper to centralize logging, avoiding repeated code in each setter.

3. Final Answer:

   Create a @Logger wrapper that prints old and new values inside wrappedValue's setter -> Option B

4. Quick Check:

   Use property wrapper to centralize logging [OK]

Hint: Wrap logging in property wrapper setter once [OK]

Common Mistakes:

• Manually adding print in every setter (repeats code)
• Using global functions instead of wrappers
• Trying to override Swift's default setter globally