Enriching your text in text views

At a glance

Project structure

Source bundle/
├── TextKitAndTextViewSampleApp/
│   ├── SwiftUI/
│   │   ├── TextKitAndTextViewSampleApp.swift
│   │   ├── Representables.swift
│   │   ├── ContentView.swift
│   │   └── Platform.swift
│   ├── InlineAttachmentsView.swift
│   ├── SectionCollapsingView.swift
│   ├── TextAttachmentView.swift
│   ├── LineNumberingView.swift
│   ├── ExclusionPathView.swift
│   └── TextListView.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── TextKitAndTextViewSampleApp.xcodeproj/
    └── .xcodesamplecode.plist

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 3 project/configuration file(s) and 40 source declaration(s).

Overall architecture

flowchart LR
    N1["TextKitAndTextViewSampleApp"]
    N2["ContentView"]
    N3["AnimatedAttachmentViewProvider"]
    N4["SwiftUI / AVKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

TextKitAndTextViewSampleApp/SwiftUI/TextKitAndTextViewSampleApp.swift:10 — architecture anchor

@main
struct TextKitAndTextViewSampleAppApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

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 UIKit.

Ownership and state

classDiagram
    InlineAttachmentsContainerView *-- PlatformTextView : textView
    AnimatedAttachmentView *-- AVPlayerView : playerView
    AnimatedAttachmentView *-- AVPlayerLayer : playerLayer
    AnimatedAttachmentView o-- AVQueuePlayer : player

Ownership evidence

TextKitAndTextViewSampleApp/InlineAttachmentsView.swift:13 — stored dependency or nearest verified ownership anchor

class InlineAttachmentsContainerView: PlatformContainerView {
    let textView = PlatformTextView()
    // ...
}

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

TextKitAndTextViewSampleApp/SwiftUI/TextKitAndTextViewSampleApp.swift:11 — representative type boundary

@main
struct TextKitAndTextViewSampleAppApp: App {
    // ...
            ContentView()
    // ...
}

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

Access control

Reference code

TextKitAndTextViewSampleApp/ExclusionPathView.swift:25 — representative boundary

    private func configureExclusionPath() {
        let bezierPath = ExclusionPath.bezierPath
        // ...
    }

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: App: TextKitAndTextViewSampleAppApp; Provider: AnimatedAttachmentViewProvider, ExpandableAttachmentViewProvider; View: AnimatedAttachmentView, AttachmentButtonView, CollapsibleTextView, ContentView, DisclosureGutterView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: layoutSubviews, loadView, attachmentBounds, viewProvider, loadInlineAttachmentSampleText, loadSampleText, setupConstraints, setupLayout.
• Files: TextKitAndTextViewSampleApp/SwiftUI/ContentView.swift.

Architecture takeaways

• TextKitAndTextViewSampleApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, AVKit 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