Handling Different Data Types in Core Data

At a glance

Project structure

Source bundle/
├── CoreDataAttributes/
│   ├── AppDelegate.swift
│   ├── Book.swift
│   ├── ColorToDataTransformer.swift
│   ├── SceneDelegate.swift
│   ├── ViewController.swift
│   ├── BookCell.swift
│   ├── SampleData.swift
│   ├── Base.lproj/
│   │   └── LaunchScreen.storyboard
│   └── CoreDataAttributes.entitlements
├── Configuration/
│   └── SampleCode.xcconfig
└── CoreDataAttributes.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 7 project/configuration file(s) and 8 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["ViewController"]
    N3["ColorToDataTransformer"]
    N4["CoreData APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

CoreDataAttributes/AppDelegate.swift:11 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
    lazy var persistentContainer: NSPersistentContainer = {
        // Register the transformer at the very beginning.
        // .colorToDataTransformer is a name defined with an NSValueTransformerName extension.
        ValueTransformer.setValueTransformer(ColorToDataTransformer(), forName: .colorToDataTransformer)

        let container = NSPersistentContainer(name: "CoreDataAttributes")
        container.loadPersistentStores(completionHandler: { (_, error) in
            guard let error = error as NSError? else { return }
            fatalError("###\(#function): Failed to load persistent stores:\(error)")
        })

        container.viewContext.automaticallyMergesChangesFromParent = true
        SampleData.generateSampleDataIfNeeded(context: container.newBackgroundContext())

        return container
    }()
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Core Data.

Ownership and state

classDiagram
    AppDelegate o-- NSPersistentContainer : persistentContainer
    func *-- String : title
    func *-- String : canonicalTitle
    func o-- UIColor : tintColor

Ownership evidence

CoreDataAttributes/AppDelegate.swift:14 — stored dependency or nearest verified ownership anchor

    lazy var persistentContainer: NSPersistentContainer = {
        // ...
        ValueTransformer.setValueTransformer(ColorToDataTransformer(), forName: .colorToDataTransformer)
        // ...
    }()

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

No source-visible execution, scheduling, or synchronization boundary was found in the indexed source.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

CoreDataAttributes/AppDelegate.swift:12 — representative type boundary

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
        ValueTransformer.setValueTransformer(ColorToDataTransformer(), forName: .colorToDataTransformer)
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

CoreDataAttributes/Book.swift:20 — representative boundary

    @nonobjc
    public class func fetchRequest() -> NSFetchRequest<Book> {
        return NSFetchRequest<Book>(entityName: "Book")
    }

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: Controller: ViewController; Delegate: AppDelegate, SceneDelegate; Transformer: ColorToDataTransformer.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, fetchRequest, keyPathsForValuesAffectingPublishMonthID, date, allowsReverseTransformation, transformedValueClass, transformedValue, reverseTransformedValue.
• Files: CoreDataAttributes/AppDelegate.swift, CoreDataAttributes/Book.swift, CoreDataAttributes/ColorToDataTransformer.swift, CoreDataAttributes/SceneDelegate.swift, CoreDataAttributes/ViewController.swift, CoreDataAttributes/BookCell.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, CoreData through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation