Recommended patterns for menus and dialogs about react-navigation.github.io

[dantman]

As I'm developing an app more and more using React Navigation I'm strongly leaning towards modals (menus and dialogs) being something StackNavigator supports.

• Handling menus and dialogs as part of params is insufficient. There are a variety of reasons one may want these separate, shared, or otherwise not polluting routes. And these grow as apps get bigger.
• Because of my need for a Drawer, screens above the drawer, and a modal StackNavigator for full-screen dialogs I already have a terribly deep and convoluted route tree. And I can say for certain that having separate navigators to handle different types of routes just makes things more complicated than they need to be.

So rather than dialogs and modals being a separate navigator I think it's better for StackNavigator to be able to handle the key points of dialogs/menus/modals/overlays:

• Routes that show the previous route in the stack below them.
• Overlay routes that don't affect the header, and.
• Routes that have a different transition style.

[brentvatne]

cc @ericvicenti - I tend to agree with @dantman's assessment here

[ericvicenti]

I really think we should be careful about adding a million features to StackNavigator.. its already getting out of hand. I have more details on my thoughts here:

react-navigation/rfcs#15