Ashoat Tevosyan

If I recall correctly, the reason we type as `React.StatelessFunctionalComponent` instead of `React.ComponentType` was because of a Flow bug. It’s been fixed in more recent versions so the libdef for...

RE not knowing how to call `createAppContainer`, try React Navigation docs, and if that doesn’t work try the canonical example project in that repo. RE missing tests, PRs are welcome....

Ah, you’re having trouble typing the call itself. I don’t have access to a laptop right now. I’ll try to get back to you when I do. For now I...

What errors do you get if you try to pass in a subtype of `NavigationState` as the first type parameter? Honestly, I don't use `createAppContainer` in my app and haven't...

I looked into whether GitHub has a feature to subscribe to any PRs on a folder, but it doesn't appear to exist. It would of course be possible for somebody...

It's admittedly non-obvious how to type a custom navigation route. Here's how it's done: ```js type NavProp = NavigationScreenProp void, |}, |}>; ``` > Also it would be nice, if...

Try `NavigationStateRoute`, and if that works take a look at its definition to see what you were doing wrong above.

Ah, interesting. Perhaps you are on an older version of Flow - can you try upgrading?

How are you using React Navigation with Flow 0.81? You’re using React Native right? Are you aware each version of React Native is tied to a specific version of Flow?

Yes, that’s correct. If you keep your `.flowconfig` updated using `react-native upgrade` or `react-native-git-upgrade`, there is a declaration at the bottom that locks in a specific Flow version. It may...