Cesare ForelliFeb 22, 2024

In AppKit/UIKit, when I get an object from a REST API I decode it, modify it, and then push the modified object back.

REST ➡️ decodedObject ➡️ decodedObject.foo = true ➡️ REST

I struggle to keep it as simple with #SwiftUI!

Let’s say I want to use a Toggle to flip decodedObject.foo, I can't because it expects a Binding, so I end up with

REST ➡️ decodedObject ➡️ .onLoad { (@ State var) fooCopy = decodedObject.foo ➡️ Toggle(isOn: $fooCopy) } ➡️ .onDisappear { decodedObject.foo = fooCopy } ➡️ REST

Show threadPaul DarceyFeb 22, 2024
@cdf1982 Could you use @Bindable on decodedObject? (I.e. is decodedObject Observable?) https://developer.apple.com/documentation/swiftui/bindable
Bindable | Apple Developer Documentation

A property wrapper type that supports creating bindings to the mutable properties of observable objects.

Apple Developer Documentation
Show threadCesare ForelliFeb 22, 2024

@pdarcey First of all, thank you!

I am not very experienced with SwiftUI, so I've only occasionally heard about @ Bindable, but reading the docs you linked to makes it clear that it is exactly what I was looking for.

I was very excited by the fact that my decodingObject was already conforming to Identifiable, but sadly making it @ Observable is not yet an option for me, because I cannot target iOS 17 yet 😭.

Still, I am happy to know that the copy variables are only a stopgap.

Thanks again!

Show threadHelge HeßFeb 22, 2024
@cdf1982 @pdarcey If you can’t use Observable, use ObservableObject. It’s the slightly less convenient predecessor.
Show threadCesare ForelliFeb 22, 2024
@helge Thank you, I'll investigate this!
Show threadHelge Heß
@cdf1982 I tend to do it in #SwiftUI more or less exactly like in AppKit/UIKit. A controller (the Observable or ObservableObject w/ Published), the View for presentation and then your models that are managed/coordinated by the controller.
Feb 22, 2024 at 11:43amWeb