Satyajit Sahoo

Just a suggestion sorry 😛

> how do you plan to solve this in v5? In v5, [`useNavigation`](https://github.com/react-navigation/navigation-ex/blob/master/packages/core/src/useNavigation.tsx) accepts an optional type parameter: ```js const navigation = useNavigation() ``` > For me all those are...

See the linked code for `useNavigation`. The code I posted gives error because there's a constraint.

It can be ported, but it'll break all existing types of v4 so probably not worth it.

Thanks for the PR! However this seems to be fixed in the docs already so I'm closing this.

we know the back button layout, so it'd be possible to set a horizontal margin of the same size. though imo truncating the title is bad. since title is for...

> overflows the screen won't be readable anyway. I would prefer it to be truncated and just see the dots overflow is worse, but that doesn't mean that truncating isn't...

> The problem is that all the elements of the header have an absolute position and no width (or max width), that's why they overlap. They are using absolute position...

Params are merged for every action, not just `setParams` or `navigate`. So I'm not sure mentioning it specifically in this example makes sense. If it wasn't obvious, maybe the better...

Thanks, I think we can add a section in this page about what happens when passing params to an existing screen: https://reactnavigation.org/docs/params