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
I have a project that consists of "integrations" with other services. These integrations are discovered and loaded using a ServiceLoader.
The interface looks like this:
interfaceIntegration: Screen {
val metadata:IntegrationMetadata
}
Every integration has its own UI and uses its own Navigator instance with their own SharedScreen sealed interface. They are completely independent of each other.
Can I somehow configure the main Navigator instance without having to define the RootSharedScreen sealed interface at compile-time that would point to the Integration?
I wanted to decouple the whole integrations from the main UI. But as it is now, I still need to hardcode the RootSharedScreen that is at level 0.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a project that consists of "integrations" with other services. These integrations are discovered and loaded using a
ServiceLoader
.The interface looks like this:
Every integration has its own UI and uses its own
Navigator
instance with their ownSharedScreen
sealed interface. They are completely independent of each other.Can I somehow configure the main
Navigator
instance without having to define theRootSharedScreen
sealed interface at compile-time that would point to theIntegration
?I wanted to decouple the whole integrations from the main UI. But as it is now, I still need to hardcode the
RootSharedScreen
that is at level 0.Beta Was this translation helpful? Give feedback.
All reactions