Add a + here please. Make sure you always do this in React props

Why don't we use our ScreenParamList here? That will makes sure navigate calls are typed correctly

I think you're introducing a regression here, where multiple presses of the close button will lead to the screen that opened CameraModal being dismissed too.

In the future, this is the type of the thing you should be able to notice before you put the diff up. When you see goBackOnce, you should ask yourself "why does this exist, and why isn't it in stock React Navigation"? If we implemented some custom functionality, there's almost certainly a good reason for that. You should not be removing that functionality without first understanding it.

Options to address this:

1. Introduce goBackOnce to ChatRouter (similar to how we do it in RootRouter and OverlayRouter), and introduce a new ProfileRouter with goBackOnce for ProfileNavigator.
2. Find another way to make sure multiple goBacks aren't triggered, eg. by using some instance variable to track if it's already been pressed.

You can't do what's done there because Flow doesn't support generics on class declarations in the same way it does for function declarations.

Options here:

1. Wrap the class declaration in a function declaration like we do with createTooltip, and then make the function declaration generic (more work than ideal and messy)
2. Convert CameraModal to a function component (way too much work for now)
3. (Best option) This doesn't actually really need to be generic, in the sense that there's nothing you need here specific to this particular route. Try replacing AppNavigationProp<'ChatCameraModal'> with one of the following:
   • AppNavigationProp<$Keys<OverlayParamList>>
   • AppNavigationProp<mixed>

If neither of those work, let me know and I'll try to patch locally and take a look.