Update types.tsx

[nikmantulenko]

I'm proposing to add better typing possibilities for custom header components

Motivation

using NativeStackHeaderProps type for 'options.header = (props: NativeStackHeaderProps) => ...
gives no type checking for route & navigation props

[github-actions]

Hey @nikmantulenko! Thanks for opening your first pull request in this repo. If you haven't already, make sure to read our contribution guidelines.

[netlify]

✅ Deploy Preview for react-navigation-example ready!

Name	Link
🔨 Latest commit	3b84583
🔍 Latest deploy log	https://app.netlify.com/sites/react-navigation-example/deploys/644a8b2f5c2d89000871fc68
😎 Deploy Preview	https://deploy-preview-11281--react-navigation-example.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[branaust]

LGTM

[osdnk]

Hi, @nikmantulenko

Thanks for the PR!

I think this might be a nice approach, but at this stage, this seems to be a very atomic change, whereas there are multiple places with a very similar approach implemented (to name a few, consider all components in the stack).

So if you are up to making the holistic migration, we will be happy to merge. Currently, we find this use case a bit rare (to have header parametrized by the route) so we will probably not spend the effort actively on implementing that. But, as stated earlier, we are happy to review the follow-up change.