react-navigation / react-navigation/react-navigation.github.io
Stack navigator for each tab code example warning
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 324
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
When running on a bare react-native project, the stack navigator for each tab code example triggers the following warning:
Found screens with the same name nested inside one another. Check:
Home, Home > Home
A similar warning is displayed when switching to the "Settings" tab.
Should the name prop of each Tab.Screen change to avoid this warning?
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
Start with the linked “A stack navigator for each tab” example and reproduce it in a bare React Native project to confirm the nested-name warning for Home and Settings. Determine the appropriate screen names, then update the example so switching tabs no longer produces the warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- documentation, mobile
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100