Passing route params as first level props about rfcs

[brentvatne]

with your proposal, how does this get passed into navigationOptions?

static navigationOptions = ({ navigation }) => {
 // how do I access params here?
}

[mtnt]

I guess, it should be considered from a purpose point of view. So since I propose it for being able to create independently (from navigation) components, it is the purpose.
If someone makes the static navigationOptions inside his component, so, I guess he don`t want to make that component independent from navigation. And params could be accessible from the navigation.params or as navigation sibling property - actually it does not matter.

[mtnt]

However I still think that route params and scene outer params should be separated. So it would be pretty good to have static navigationOptions({navigation, routeParams, innerParams}) or something similar.

[satya164]

React Navigation 5 passes a route object as a prop which makes accessing the params shorter (route.params as opposed to navigation.state.params).

Passing params as to-level props doesn't make components any independent of the navigation library since you still use the navigation prop which is specific to the library. To make something really independent and reusable, we'd have to extract it out to a separate components, abstract these methods out and pass them.

Passing params as top-level props also means that we can't add any more props to screens in future since there's now a chance of conflicts.

Closing since this is not something we'll implement.