Skip to content
Discussion options

You must be logged in to vote

Yes. Since your Integration already extends Screen, the object discovered by ServiceLoader can be pushed directly. A RootSharedScreen hierarchy is not required by Navigator:

fun openIntegration(
    rootNavigator: Navigator,
    integration: Integration,
) {
    rootNavigator.push(integration)
}

Call this from the integration picker using the root navigator. Voyager invokes the selected integration's Content(); that content can create its own nested Navigator exactly as it does now.

The SharedScreen : ScreenProvider pattern in the multi-module guide is an optional lookup layer: ScreenRegistry maps a provider to a concrete Screen, which is then passed to push. Your service discovery alread…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by mainrs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants