react-navigation / react-navigation/react-navigation.github.io
Clarify the example in # Navigation actions are handled by current navigator and bubble up if couldn't be handled
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 324
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
In the above example, when calling navigate('Settings'), inside Profile screen, the nested stack navigator will handle it, but if you call navigate('Home'), the parent tab navigator will handle it.
This example doesn't sound right to me but not sure how to correct it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked navigation-actions section and the quoted example first. Compare the stated navigate('Settings') and navigate('Home') behavior with the surrounding nesting documentation; done means the example clearly and accurately explains which navigator handles each action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, react-native
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100