One nice thing about this is that typed hooks like `useNavigation` also handle navigator nesting.
So if you use typed hooks instead, you don't need to combine navigation props manually. So no explicit `CompositeNavigationProp` or `CompositeScreenProps`.
It's automatically handled under the hood. So the manual types for your dynamic navigation structure also get much simpler.
React Navigation 8 brings rich types to `useNavigation` and `useNavigationState` β¨
So far, that only worked with the static API. Now we're bringing it to the dynamic API too π
It won't be automatic like static config, but there was no way we were leaving it out πͺ