Hello!! Is it possible to add functionality to disable animation on a single navigate call?

Would like to be able to disable animations when open drawer, open instant without animation (when use DrawerOpen) thanks.

When using a typed stack navigation there are no type warnings for the event being dispatched. e.g. const navigation = useNavigation<StackNavigationProp<'Stack.ScreenName'>>() const goToScreen = () => { navigation.dispatch(StackActions.push('Stack.AnotherScreenName')) } Some way to specify a type which will check that the arguments provided to the event creator or event dispatch are valid. I would expect this to be fairly manual, e.g. type StackScreenArgs = { 'ScreenName': { arg1: number; arg2: number; }; } navigation.dispatch( StackActions.push<StackScreenArgs>('ScreenName', {...screenArgs}) )

being able to have a permanent drawer is great, but I'd love to provide a way to still open/close the drawer programmatically in some cases. For example: when a user of an app is writing a post focus on the writing screen and remove the sidebar as a distraction. give the users an ability to hide or show the navigation as needed via an icon (see the Bear notes app)

See the following issues for a detailed description of the problem, and a workaround: https://github.com/react-navigation/react-navigation/issues/9744

Currently Stack Navigator render on screen at a time, which is perfectly fine with mobile interface, but in web UI seems unusual because of space available, So I want that we can make funtionality to render certain number of stack screen at the same time, like for web when navigate to screen in a stack previous screen width becomes 60% of total from 100%, and new screen comes side by side as a stack (web whatsapp for reference), we can add a prop to options to configure how many screen to render in stack, and there should be a threshold, like assume it's 2 so when the stack length is greater than 2 it will replace the last render stack view

When a device is put into landscape, the option should be available to move the tab navigator to the side of the screen.

I have submitted a fix here: https://github.com/ntdiary/react-navigation/commit/b43b386f30f5eaf84c07100dc233c81b8eaa92e2 we couldn't know exactly when the transition will end, because InteractionManager.runAfterInteractions() is not working properly on the web platform. I'm not quite sure if this is an issue or a feature. Hope we can improve it. And I temporarily changed the example demo to demonstrate. Glad to contribute if posible 🙂

@gorhom was nice enough to create a patch for this. https://github.com/gorhom/react-navigation-scrollable-modal This would enable users to swipe a modal away when the scrollable content is at its top position. This is how scrollable content inside of modals behave on native iOS apps out of the box. It is a highly coveted feature and how people who come from the Swift expect modals to behave in react native. Here is a video of this in action. https://twitter.com/Gorhom/status/1436777114540380173?s=20

On tablet in portrait mode it should be awesome to have a tab bar at the bottom and a 1/3 pane left with a list container and at the right side of this pane a 2/3 pane with the detail view of the selection of the list item from the 1/3 part. On tablet in landscape mode, the tab bar should be better aligned at the left of the screen, and still having the 1/3 + 2/3 screen pane ratio. Actually, to be more clear it is a master(list) + detail layout.