ericvicenti/navigation-rfc

Doc Improvement: Custom reducers should clearly be encouraged/supported

Open

#5 opened on Jan 4, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees) (44 forks)github user discovery
help wanted

Repository metrics

Stars
 (440 stars)
PR merge metrics
 (PR metrics pending)

Description

I'd love to see a documented support for providing this navigation model a custom reducer / onNavigation method which is propagated to build in or library provided Components like NavigationCard or NavigationHeader.

The docs currently make it sound like there is only a bunch of default actions, which could be extended, but the only supported reducer is NavigationReducer. Is that the case?

Contributor guide

Research direction
Examine the current navigation reducer in the codebase and see how it handles actions. Research how popular React Native navigation libraries (e.g., React Navigation) support custom reducers or onNavigation methods. Propose documentation updates that clearly show how to provide a custom reducer or onNavigation function to NavigationCard or NavigationHeader.
Tech stack
reactreact native
Domain
mobile
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
React NativeGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75