SwiftUI loading states with a twist; Solving a mutation puzzle
swiftindepth.com
SwiftUI loading states with a twist; Solving a mutation puzzle
It appears we can’t really escape the fact that we have to bridge an associated value to a binding. Something as straight-forward and simple in UIKit, such as using a LoadingState enum, becomes an exercise of patching some holes in SwiftUI.
SwiftUI loading states with a twist; Solving a mutation puzzle
High bit, as it relates to how i’m doing things seems to be: Give LoadableSubject an idea of the domain it’s modelling… perhaps save the interactor function that loads the domains data and the interactor function that updates the domains data in state so that every loadable subject as a .subscribe that already knows what to call and a .update that already knows what to call and as always, is just responsible for setting loading states