SwiftData setup (modern persistence) in iOS Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the framework needed for SwiftData.

iOS Swift

import [1]

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

ASwiftData

BFoundation

CUIKit

DSwiftUI

Attempts:

3 left

💡 Hint

Common Mistakes

Importing UIKit or SwiftUI instead of SwiftData.

Forgetting to import any framework.

You need to import SwiftData to use the modern persistence features.

2fill in blank

medium

Complete the code to declare a SwiftData model class named 'Note'.

iOS Swift

@Model
class [1] {
  var text: String
  init(text: String) {
    self.text = text
  }
}

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

ANoteModel

Bnote

CNote

DNotes

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase 'note' for the class name.

Using plural 'Notes' for a single model.

The model class should be named Note with a capital N to follow Swift naming conventions.

3fill in blank

hard

Fix the error in the code to create a SwiftData container in the app struct.

iOS Swift

var body: some Scene {
  WindowGroup {
    ContentView()
      .modelContainer(for: [1].self)
  }
}

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

Anote

BNote

CNotes

DNoteModel

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or plural names that don't match the model class.

Forgetting to add .self after the model name.

The model container needs the model type Note.self with the exact class name.

4fill in blank

hard

Fill both blanks to declare a SwiftData model with an integer id and a string title.

iOS Swift

@Model
class Task {
  var id: [1]
  var title: [2]
  init(id: Int, title: String) {
    self.id = id
    self.title = title
  }
}

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

AInt

BString

CDouble

DBool

Attempts:

3 left

💡 Hint

Common Mistakes

Using String for id or Int for title.

Using unsupported types like Double or Bool here.

The id should be an Int and the title a String.

5fill in blank

hard

Fill all three blanks to create a SwiftData model with a UUID id, a string name, and a boolean done flag.

iOS Swift

@Model
class Item {
  var id: [1] = [2]()
  var name: [3]
  var done: Bool = false
  init(name: String) {
    self.name = name
  }
}

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

AUUID

CString

DInt

Attempts:

3 left

💡 Hint

Common Mistakes

Using Int for id instead of UUID.

Not initializing UUID with UUID().

Using Int for name instead of String.

The id is a UUID initialized with UUID(), and name is a String.

Practice

1. What is the purpose of marking a class with @Model in SwiftData?

easy

A. It disables saving data for that class.

B. It makes the class visible only to the current view.

C. It tells SwiftData to manage and save instances of that class automatically.

D. It converts the class into a SwiftUI view.

Solution

1. Step 1: Understand the role of @Model

   The @Model attribute marks a class as a data model for SwiftData to manage persistence.

2. Step 2: Recognize automatic data management

   SwiftData automatically saves and tracks changes for classes marked with @Model.

3. Final Answer:

   It tells SwiftData to manage and save instances of that class automatically. -> Option C

4. Quick Check:

   @Model means automatic data management [OK]

Hint: Remember: @Model means SwiftData saves your data class [OK]

Common Mistakes:

• Thinking @Model creates a UI component
• Assuming @Model disables saving
• Confusing @Model with view modifiers

2. Which of the following is the correct way to set up a SwiftData model container in your app's main entry point?

easy

A. let container = ModelContainer(for: MyModel.self)

B. let container = .modelContainer(for: MyModel.self)

C. let container = ModelContainer(for: [MyModel].self)

D. let container = .modelContainer(for: [MyModel].self)

Solution

1. Step 1: Recall the correct syntax for model container setup

   SwiftData uses ModelContainer(for: MyModel.self) to create a container for a single model type.

2. Step 2: Identify the correct option

   let container = ModelContainer(for: MyModel.self) uses the correct constructor syntax.

3. Final Answer:

   let container = ModelContainer(for: MyModel.self) -> Option A

4. Quick Check:

   Model container setup uses ModelContainer(for: Type.self) [OK]

Hint: ModelContainer(for: MyModel.self) [OK]

Common Mistakes:

• Using [MyModel].self array syntax incorrectly
• Using .modelContainer() which is a view modifier
• Forgetting .self after the type

3. Given this SwiftUI view using SwiftData:

struct ContentView: View {
  @Environment(\.modelContext) private var context
  @Query var items: [Item]

  var body: some View {
    List(items) { item in
      Text(item.name)
    }
  }
}

What will happen if you add a new Item to context?

medium

A. The new item will be saved but not displayed in the list.

B. The list will not update until the app restarts.

C. The app will crash because @Query cannot detect changes.

D. The list will automatically update to show the new item.

Solution

1. Step 1: Understand @Query and @Environment(\.modelContext)

   @Query fetches data from the model container and updates the view automatically when data changes.

2. Step 2: Recognize automatic UI updates

   Adding a new Item to context triggers the @Query to refresh, updating the list.

3. Final Answer:

   The list will automatically update to show the new item. -> Option D

4. Quick Check:

   @Query updates UI on data change [OK]

Hint: @Query auto-refreshes UI when data changes [OK]

Common Mistakes:

• Thinking UI updates only on app restart
• Believing @Query is static data
• Assuming app crashes on data change

4. You wrote this code but your app crashes at runtime:

@Model
class Task {
  var title: String
  init(title: String) {
    self.title = title
  }
}

What is the likely cause of the crash?

medium

A. The class is missing a default initializer for SwiftData.

B. You must mark the class as final when using @Model.

C. The property title must be optional.

D. You cannot use classes with @Model, only structs.

Solution

1. Step 1: Check SwiftData model requirements

   SwiftData requires model classes to have a default initializer or all properties to have default values.

2. Step 2: Identify missing default initializer

   The class has a custom initializer but no default one, causing runtime issues.

3. Final Answer:

   The class is missing a default initializer for SwiftData. -> Option A

4. Quick Check:

   SwiftData models need default initializers [OK]

Hint: Ensure @Model classes have default initializers [OK]

Common Mistakes:

• Thinking @Model requires final keyword
• Making properties optional unnecessarily
• Believing only structs can be @Model

5. You want to create a SwiftData model for a Book with a title and optional author. You also want to fetch all books with a non-empty author in a SwiftUI view. Which code snippet correctly defines the model and query?

hard

A. @Model
class Book {
var title: String
var author: String
init() { title = ""; author = "" }
}
@Query(filter: #Predicate { $0.author != "" }) var books: [Book]

B. @Model
class Book {
var title: String = ""
var author: String? = nil
}
@Query(filter: #Predicate { $0.author != nil && !$0.author!.isEmpty }) var books: [Book]

C. @Model
class Book {
var title: String
var author: String?
}
@Query(filter: #Predicate { $0.author != nil }) var books: [Book]

D. @Model
class Book {
var title: String = ""
var author: String = ""
}
@Query(filter: #Predicate { $0.author.isEmpty }) var books: [Book]

Solution

1. Step 1: Define model with optional author and default values

   @Model
   class Book {
     var title: String = ""
     var author: String? = nil
   }

   @Query(filter: #Predicate { $0.author != nil && !$0.author!.isEmpty }) var books: [Book]

   correctly defines author as optional with a default nil and title with a default empty string.

2. Step 2: Use a filter predicate to fetch books with non-empty author

   The filter checks author != nil and that author is not empty, matching the requirement.

3. Final Answer:

   Correctly defines the model and query for non-empty authors. -> Option B

4. Quick Check:

   Optional author + filter for non-empty =

   @Model
   class Book {
     var title: String = ""
     var author: String? = nil
   }

   @Query(filter: #Predicate { $0.author != nil && !$0.author!.isEmpty }) var books: [Book]

   [OK]

Hint: Use optional property and filter for non-empty string [OK]

Common Mistakes:

• Forgetting to make author optional
• Using empty string author without optional
• Incorrect filter logic for non-empty strings