เชื่อม Combine เข้ากับ SwiftUI

Combine produces a stream of values over time, while SwiftUI redraws from state. Bridging the two means feeding that stream into state.

SwiftUI only re-renders when an observed property changes, so to update the screen a publisher must ultimately write into such a property.

The assign subscriber writes each value straight into a property using a key path, no closure needed.

Put your published properties in an @Observable model class, then let Combine update them as values arrive.

Keep subscriptions alive by storing each cancellable in a set that lives as long as the model.

In a sink, assign the received value to a state property, and SwiftUI redraws on the next run loop.

UI updates must happen on the main thread, so use receive(on:) before delivering values to state.

Bind a TextField to a model property, then publish its changes so a Combine pipeline can react to typing.

Capture self weakly inside sink closures so the model is not kept alive by its own subscription.

Modern code often pairs Combine for input with async/await for the network call inside the pipeline.

The pattern is steady: publisher to operators to sink or assign, landing values in observable state. 🌉

You connected Combine to SwiftUI: pipe values through operators, hop to the main thread, and land them in observable state. 🎉