/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

0 vote368 views1 answer
Remarkable react js
Javascript React
15 votes335 views3 answers
React native expo navigation
Javascript React
7 votes324 views2 answers
Hover react
Javascript React
3 votes371 views1 answer
React router Link does work
Javascript React
0 vote342 views1 answer
Libraries like html-react-parser
Javascript React
68 votes388 views4 answers
Inline style react
Javascript React
1 vote359 views1 answer
Docker react module not found
Javascript React
1 vote349 views1 answer
React emoji picker
Javascript React
1 vote373 views1 answer
React connect production
Javascript React
1 vote372 views1 answer
Div onchange react
Javascript React