Satyajit Sahoo

Thanks for the PR, however, the types don't allow to pass anything other than a string. While passing a react element works right now it's not supported and can break...

Thanks for the PR. However "stays to that screen" doesn't seem grammatically correct so it seems more confusing. I'm closing this since it's an old PR, but feel free to...

Thanks for the PR. We now have a full example with Firebase dynamic links: https://reactnavigation.org/docs/deep-linking/#third-party-integrations So I'm closing this.

Feel free to send a PR to remove the "full screen modal" terminology from this screen. This page is supposed to cover the general usage of modals, regardless of whether...

Thanks for the PR. I'm closing this since this change is for an older version of React Navigation. Feel free to send a new PR for the current version of...

Thanks for the PR. However this seems to be fixed, so I'm closing this.

@dimaqq you realize that the issue is opened by the author of the project, right?

> is there any combination of hooks that we can use to listen to be sure the RootNavigator is in the authenticated state, then navigate to our desired screen The...

From 6.x onwards, we started warning if you have the same name for the immediately nested screen. I'm closing this since this isn't a recommended pattern, and the main problem...

IMO `useNavigation` should take the type of navigation prop as the generic instead of `S` (?): ```ts const navigation = useNavigation(); ``` cc @slorber