react-navigation / react-navigation/react-navigation.github.io
Clarify what is valid as a `screen` in `RouteConfigs`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 324
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/react-navigation/react-navigation/issues/3143 shows that there is some confusion about nesting navigators as screens. This will probably require improving the API to make this more ergonomic, but for now we should at least make this super clear.
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 by reviewing the RouteConfigs documentation and the linked issue about nesting navigators as screens. Determine which screen values are currently valid and how nested navigators should be described. Done means the documentation clearly explains the supported configuration and removes the reported confusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, react-native
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100