Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Observation #547

Open
1 of 4 tasks
RichLogan opened this issue Jan 8, 2025 · 0 comments
Open
1 of 4 tasks

Observation #547

RichLogan opened this issue Jan 8, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@RichLogan
Copy link
Collaborator

RichLogan commented Jan 8, 2025

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
@RichLogan RichLogan added the enhancement New feature or request label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant