react-navigation / react-navigation/react-navigation.github.io
Clarification request: why not store navigation state in redux?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 324
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
From the docs:
Can I store the navigation state in Redux too?
This is not possible. We don't support it because it's too easy to shoot yourself in the foot and slow down / break your app.
How exactly does someone shoot herself/himself in the foot with by doing this? Why does this slow down / break the app?
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 Redux integration section linked in the issue, especially the question about storing navigation state in Redux. Trace the documented constraints and add a clear explanation of how doing so can slow down or break an app; update the documentation when the rationale is supported by the project’s guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, react-native, redux
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100