react-navigation / react-navigation/react-navigation.github.io

Issue with `Opening a Full Screen Modal`?

Ouverte
#59 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@brentvatne y travaille déjà.

Depuis le 15/2/2018.

Langage dominant
JavaScript
Étoiles
324
Forks
2k
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.