Document how to render conditional child navigation

Hi. In my team we’ve struggled to implement conditional child navigation, where a branch of the navigation depends on user data (e.g. data in Redux and/or received from an API). In pseudo-code:

const Section1Default = StackNavigator(/* Some screens */)
const Section1Onboarding = StackNavigator(/* Different screens */)

const RootNavigator = TabNavigator({
  section1: Section1Default OR Section1Onboarding,
  section2: …,
  section3: …
})

The idea is that when clicking on a specific tab, the user should see either a series of "onboarding" screens or the feature’s screens. (Both options are navigators themselves, but could be single screens too.)

@brentvatne & @ericvicenti Do you think that’s a use case worth addressing in the docs?
I think I could contribute a page section or a page on this, but I’m not sure what solution to offer.

So far we’ve only found hackish workarounds, such as: a wrapper component which has a StackRouter with the two navigation branches, and which navigates to the correct branch on willFocus. It works, but the trick falls short when using the Android back button.

No se nombra ningún archivo de documentación, prueba ni punto de entrada. Empieza revisando la documentación de navegación existente y la solución alternativa reportada basada en un componente wrapper; después, verifica cómo interactúan los navegadores secundarios condicionales con el botón Atrás de Android. Se considera completado cuando se documente un patrón acordado y compatible para elegir la navegación de onboarding o de funcionalidades a partir de los datos del usuario.