The existing Redux "Basics/Advanced" tutorial sequence desperately needs to be rewritten. While it's been useful for many people, the target audience of the Redux docs has changed considerably since Dan first put it together. At the time, Dan said:
So hard to write the new docs. Many different audiences to cater to.
Should make sense to: Flux beginners, FP people, FP people who don't get Flux, Flux people who don't get FP, normal JS people too
Flux people: "is this proper Flux?" FP people: "is this that weird thing called Flux?" Normal people: "why not Backbone"
Clearly, the audience today is very different.
Flaws with the Tutorial
Goals
My main goals here are:
Drop all outdated references ("Flux", "containers", etc)
Show simpler patterns (inline action types like {type: "todos/addTodo"} vs const ADD_TODO = "ADD_TODO", single-file Redux logic)
Overview
The existing Redux "Basics/Advanced" tutorial sequence desperately needs to be rewritten. While it's been useful for many people, the target audience of the Redux docs has changed considerably since Dan first put it together. At the time, Dan said:
Clearly, the audience today is very different.
Flaws with the Tutorial
Goals
My main goals here are:
{type: "todos/addTodo"}
vsconst ADD_TODO = "ADD_TODO"
, single-file Redux logic)Existing Redux Tutorial Sequence Notes
Previous Personal Notes
Feedback
Introduction
Basics
/basics
- should be/tutorials/something
Actions
const ADD_TODO = 'ADD_TODO'
type
property that indicates the type of action being performed"payload
moreindex
instead of the whole todo", but rephrase this somehowdispatch
and none of that's been mentioned yetReducers
normalizr
instead of our own docs pageObject.assign({}, state, arg)
: ew!Object.assign()
warning (ES6? really?)immutability-helper
,updeep
, andImmutable.js
combineReducers
/ imports / reducer naming are a bit confusing