Why Custom validation property wrappers in Swift? - Purpose & Use Cases

The Big Idea

What if you could stop repeating validation code and let Swift do it for you automatically?

The Scenario

Imagine you have to check many user inputs like names, emails, or passwords manually every time you get new data in your app.

You write the same checks over and over in different places, making your code long and messy.

The Problem

Manually validating each property means repeating code everywhere, which is slow and easy to forget.

It also makes your app buggy because one missed check can cause wrong data to sneak in.

The Solution

Custom validation property wrappers let you write validation rules once and reuse them easily.

They keep your code clean and safe by automatically checking values whenever they change.

Before vs After

✗ Before

var email: String = "" {
  didSet {
    if !email.contains("@") {
      email = oldValue
    }
  }
}

✓ After

@EmailValidated var email: String

What It Enables

You can build safer apps faster by automatically enforcing rules on your data with less code.

Real Life Example

When users sign up, their email and password are checked instantly and correctly without repeating validation code everywhere.

Key Takeaways

Manual checks are repetitive and error-prone.

Property wrappers let you write validation once and reuse it.

This keeps your code clean and your data safe.

Practice

1. What is the main purpose of a custom validation property wrapper in Swift?

easy

A. To automatically check and enforce rules on property values

B. To change the type of a property at runtime

C. To make properties private and inaccessible

D. To store multiple values in a single property

Solution

1. Step 1: Understand property wrappers

   Property wrappers in Swift add extra behavior to properties, such as validation.

2. Step 2: Identify validation role

   Custom validation wrappers check if values meet certain rules before storing them.

3. Final Answer:

   To automatically check and enforce rules on property values -> Option A

4. Quick Check:

   Validation = enforce rules [OK]

Hint: Validation wrappers enforce rules on data automatically [OK]

Common Mistakes:

• Thinking wrappers change property type
• Confusing validation with access control
• Assuming wrappers store multiple values

2. Which of the following is the correct syntax to declare a custom validation property wrapper named NonEmpty for a String property in Swift?

easy

A. var name: @NonEmpty String

B. var @NonEmpty name: String

C. @NonEmpty var name: String

D. NonEmpty var name: String

Solution

1. Step 1: Recall property wrapper syntax

   In Swift, property wrappers are applied with @ before the wrapper name, placed before the variable declaration.

2. Step 2: Match correct syntax

   Correct syntax is @WrapperName var propertyName: Type, so @NonEmpty var name: String is correct.

3. Final Answer:

   @NonEmpty var name: String -> Option C

4. Quick Check:

   @WrapperName before var = correct syntax [OK]

Hint: Use @ before wrapper name, then var property [OK]

Common Mistakes:

• Placing @ after var
• Putting wrapper inside type
• Omitting @ symbol

3. Consider this Swift code using a custom validation property wrapper Positive that only allows positive integers:

 @propertyWrapper
 struct Positive {
     private var value: Int = 1
     var wrappedValue: Int {
         get { value }
         set { value = newValue > 0 ? newValue : 1 }
     }
 }

 struct Account {
     @Positive var balance: Int
 }

 let acc = Account()
 print(acc.balance)

What will be printed when this code runs?

medium

A. 1

B. 0

C. nil

D. Compilation error

Solution

1. Step 1: Understand default value in wrapper

   The wrapper's private value starts at 1, and sets new values only if positive; else resets to 1.

2. Step 2: Check initial property value

   Account's balance uses @Positive but no initial value is set, so it uses wrapper's default 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Default wrapper value = 1 [OK]

Hint: Default wrapper value used if no initial value given [OK]

Common Mistakes:

• Expecting 0 as default
• Assuming nil is possible
• Thinking code won't compile

4. This Swift code attempts to create a custom validation property wrapper NonNegative but has an error:

 @propertyWrapper
 struct NonNegative {
     var value: Int
     var wrappedValue: Int {
         get { value }
         set { if newValue >= 0 { value = newValue } }
     }
 }

 struct Score {
     @NonNegative var points: Int = -5
 }

What is the main problem causing this code to fail?

medium

A. wrappedValue setter does not handle negative values correctly

B. Property wrapper lacks an initializer to set initial value

C. Cannot assign default value to property with wrapper

D. Missing @ symbol before property wrapper

Solution

1. Step 1: Check property wrapper requirements

   Property wrappers must have an init(wrappedValue:) to accept initial values.

2. Step 2: Identify missing initializer

   NonNegative lacks init(wrappedValue:) so compiler cannot assign -5 to points.

3. Final Answer:

   Property wrapper lacks an initializer to set initial value -> Option B

4. Quick Check:

   Missing init(wrappedValue:) = error [OK]

Hint: Add init(wrappedValue:) to accept initial values [OK]

Common Mistakes:

• Ignoring missing initializer
• Blaming setter logic
• Thinking default value assignment is invalid

5. You want to create a custom validation property wrapper LimitedLength that limits a String property's length to a maximum number of characters. Which of the following implementations correctly enforces this limit and allows setting the max length when declaring the property?

 @propertyWrapper
 struct LimitedLength {
     private var value: String = ""
     private let maxLength: Int

     var wrappedValue: String {
         get { value }
         set {
             if newValue.count <= maxLength {
                 value = newValue
             } else {
                 value = String(newValue.prefix(maxLength))
             }
         }
     }

     // Which initializer is correct?
     ???
 }

 struct User {
     @LimitedLength(maxLength: 5) var username: String
 }

hard

A. init(maxLength: Int) { self.maxLength = maxLength }

B. init(wrappedValue: String) { self.value = wrappedValue; maxLength = 5 }

C. init() { maxLength = 5 }

D. init(wrappedValue: String, maxLength: Int) { self.maxLength = maxLength; self.value = wrappedValue }

Solution

1. Step 1: Understand property wrapper initialization with parameters

   When a wrapper has parameters and initial value, it needs init(wrappedValue:maxLength:) to accept both.

2. Step 2: Match initializer to usage

   Usage passes maxLength: 5 and no initial value, so init(wrappedValue:maxLength:) fits best to set both.

3. Final Answer:

   init(wrappedValue: String, maxLength: Int) { self.maxLength = maxLength; self.value = wrappedValue } -> Option D

4. Quick Check:

   Use init(wrappedValue:maxLength:) for parameters [OK]

Hint: Use init(wrappedValue:maxLength:) to accept value and limit [OK]

Common Mistakes:

• Using init(maxLength:) only misses initial value
• Using init() without parameters
• Using init(wrappedValue:) without maxLength