aksonov/react-native-router-flux

RNRF v5 development - help wanted!

Open

#3655 opened on Apr 18, 2020

View on GitHub
 (1 comment) (19 reactions) (0 assignees)JavaScript (8,999 stars) (2,112 forks)batch import
help wanted

Description

Hello folks!

Recent React Navigation v5 has similar syntax to RNRF but it still requires definition of separate variables for every nested stack/tab, it is not convenient.

I've started RNRF v5 development (full rewriting to use React Navigation v5), but really need help to complete this huge task.

Benefits comparing to RN v5:

  • The same RNRF API as for previous versions, you don't need to rewrite your app!
  • Latest features from RN v5
  • Define all scenes in one place. No need to define separate variable as RN v5 does
  • Define onEnter/onExit actions in one place (like in v4 ). For v5 I'm planning to integrate state machine - https://xstate.js.org, so you may define authentication and other workflows together with your screens

You may check https://github.com/aksonov/react-native-router-flux/tree/v5 as prototype, it supports now pretty limited actions and props, but already works and I'm using it in one my new project

Contributor guide

Tech stack
javascriptreact
Domain
mobile
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
React Navigation v5React NativeJavaScriptxstate
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Look at the v5 branch prototype at https://github.com/aksonov/react native router flux/tree/v5 to understand current implementation. Identify missing features from the original RNRF API that need to be ported. Discuss with maintainer to prioritize tasks. Consider integrating xstate for state machine support as planned.