faceyspacey/redux-first-router

Build 3rd party plugins that optimize Sagas usage (following this blueprint) [and another for Redux-Observable]

Open

#76 opened on Aug 9, 2017

View on GitHub
 (22 comments) (1 reaction) (0 assignees)JavaScript (1,568 stars) (167 forks)batch import
help wantedinvalidwontfix

Description

Would like to get some ideas from the community on ways to improve the experience of using redux-first-router with redux-saga.

Some thoughts:

  1. Adding a reference to a saga to fire before firing our action dispatch?
  2. Another export from connectRoutes that gets added to our sagas, effectively mapping them to each route?

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
unclear
Prerequisites
Redux basicsredux sagaredux first router
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Review the 22 comments for proposed approaches. The issue requests building a plugin to integrate redux first router with redux saga, similar to a blueprint. Examine the existing codebase, particularly the connectRoutes export, to understand how sagas could be mapped to routes. No linked PRs exist.
Build 3rd party plugins that optimize Sagas usage (following this blueprint) [and another for Redux-Observable] · faceyspacey/redux-first-router#76 | Good First Issue