/Javascript/React/React native getting old navigation parameter

React native getting old navigation parameter

The problem here is how navigation.navigate works. If you use it without
passing the key for the next screen, react-navigation won't match it with the 
screen that is already mounted hence mounting another one.

What you can observe here is exactly the case when the component was not yet 
unmounted but navigate doesn't know that and renders another instance of the 
same component.

You can prevent this by passing the key param into navigate function as follows:

navigation.navigate({name: 'ScreenB', key: 'ScreenB', params: { id: 1}})

navigation.navigate({name: 'ScreenB', key: 'ScreenB', params: { id: 2}})

Now StackNavigator can check if screen with the same key already exists and 
prevent it from mounting.

Similar codes

1 vote129 views1 answer
React js component parameters
Javascript React
0 vote134 views1 answer
React how to block render if data is not fetched yet
Javascript React
3 votes139 views2 answers
Discord.js react to message
Javascript React
4 votes131 views1 answer
How to send axios delete to the backend reactjs
Javascript React
0 vote119 views1 answer
React Native Segmented Control Tab
Javascript React
-1 vote137 views1 answer
How to insert divider in react native
Javascript React
1 vote125 views1 answer
Detect touch react
Javascript React
3 votes125 views2 answers
How to get custom attribute value in react
Javascript React
1 vote177 views1 answer
React site warning: The href attribute requires a valid address. Provide a valid, navigable address as the href value jsx-a11y/anchor-is-valid
Javascript React
0 vote131 views1 answer
Nextjs react native web typescript
Javascript React