Hi there, wondering if anyone has a nice pattern for the following kind of situation:
We have a UI component which is reusable across several features, and whose state is buried several layers deep inside the controlling feature's state. The component's behavior depends on a feature flag. Feature flags come from an external system via a @Dependency, which is injected at the higher feature level. We want to avoid every high-level feature needing to be aware of the flag specifics which control this shared component's behavior Since the flag controls (in this case) a show/no-show decision within SwiftUI, we could arrange for SwiftUI's @Environment to be aware of this and not have to plumb the actual boolean value down through several layers of nested state. But this seems counter to TCA best-practices.
Any thoughts?
Thanks!