react-navigation / react-navigation/react-navigation.github.io
Navigate with key vs push
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 324
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
We should document how and why you might use navigate with a key in order to avoid pushing a route multiple times if you use the push action.
We might want to also create a specific page about routes being pushed multiple times and direct it to wherever we document this.
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
No file or test is named. Start by locating the documentation for navigate and push, then check how route duplication is currently explained. Done means documenting when to use navigate with a key and either adding or linking a focused page about routes being pushed multiple times.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, react-native
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100