react-navigation / react-navigation/react-navigation.github.io
Issue with `Opening a Full Screen Modal`?
@brentvatne ya está trabajando en esto.
Desde el 15/2/2018.
- Lenguaje dominante
- JavaScript
- Estrellas
- 324
- Forks
- 2k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
The website documentation has a section on "Opening a Full Screen Modal" (here).
The method described is to have two child Stack Navigators with a shared parent. The children are created with mode: "modal" and mode: "card", respectively.
Given this setup, let's assume a user opens an app to a card Screen. As soon he navigates to a modal screen, wouldn't the modal StackNavigator contain an unwanted screen at the root of its stack -- the screen that StackNavigator created by default as the initial route? Of course it's possible to provide an initialRouteName, but in this scenario, it doesn't make sense to do so. The modal navigator's screens are not meant to be shown in succession, and hence, this navigator has no conceptual initial route.
Is there a way to address this that I am missing? It seems like the documented approach would create problems with back behavior given the existence of the initial screen at the root of the modal StackNavigator.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.