You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to give more insight into the internals of the publications and subscriptions, some of their internals need to be exposed to the UI layer. The best way to do this is add @Observable capabilities to these objects. However, this does introduce the constraints of some of these objects needing to worry about the main thread, when previously they didn't.
My current thinking is to provide Observable* child implementations of the original types that deal with any required dispatching, leaving the original types unencumbered.
This will also cleanup some of the anti-patterns in the SwiftUI code, and callbacks that have been added to shim the observer pattern in up to this point.
SubscriptionSets
Subscriptions
Publications
CallController
The text was updated successfully, but these errors were encountered:
In order to give more insight into the internals of the publications and subscriptions, some of their internals need to be exposed to the UI layer. The best way to do this is add
@Observable
capabilities to these objects. However, this does introduce the constraints of some of these objects needing to worry about the main thread, when previously they didn't.My current thinking is to provide Observable* child implementations of the original types that deal with any required dispatching, leaving the original types unencumbered.
This will also cleanup some of the anti-patterns in the SwiftUI code, and callbacks that have been added to shim the observer pattern in up to this point.
The text was updated successfully, but these errors were encountered: