Intro to Redux

Early App Methodologies

MVC

  • M - Model - The data involved in your application
  • C - Controller - The programming that uses that data (App/Business Logic)
  • V - View - The Code for the UI

 

  • Sometimes we made hybrid structures, like view-controllers
    • This is why you'll hear the term MVVM, MVVC
      • became known as MV*
  • React is a View-layer technology
  • To have more structure to our apps we need more than a view layer... there is no control of events/data flow here!

Flux Methodologies

Data Flow

  • Data flow is important in an app
    • The order in which things happen is important
    • You don't want race conditions to occur
  • In the SPAs Angular 1 took an early lead with developers due to its two-way data binding and watch abilities
  • Issue was that that could rack up lots of watchers in your application, even though Angular 1 cleans them up for you, to an extent.
  • Watchers could 'go stale'
  • Facebook decided to approach the problem differently, using one-way data flow
  • Facebook looked to an older methodology called Flux

Flux

UI Controllers

Stores

Basket

Products

List

Account Options

Products

User

Account

Staff

Meet the staff

D

i

s

p

a

t

c

h

e

r

A

c

t

i

o

n

 

C

r

e

a

t

o

r

s

{

type: 'START_SALE'

}

{

type: 'ADD_STAFF',

name: 'Phoebe Jones'

}

Actions

P

a

g

e

UI Events

Redux

Simplifying the model

Docs: https://redux.js.org/

UI Controllers

Store

Basket

Products

List

Account Options

Products

User

Account

Staff

Meet the staff

A

c

t

i

o

n

 

C

r

e

a

t

o

r

s

{

type: 'START_SALE'

}

{

type: 'ADD_STAFF',

name: 'Phoebe Jones'

}

Actions

P

a

g

e

UI Events

Principles of Redux

  1. Single Source of Truth - one central store
  2. State is read-only
  3. Changes to state are made with 'pure functions'

Concepts Demo

Connecting with React

  • There is a package called react-redux (https://react-redux.js.org)
  • You import it into the component you want to have access to the store and you hook it up to the values of the store and the dispatch method of the store, via a function called 'connect'
  • connect needs 2 things from you:
    • mapStateToProps
    • mapDispatchToProps
import { deleteCar } from './actions'
// Here 'state' is the whole redux store
const mapStateToProps = (state, componentsProps) => ({
  items: state.cars // the cars in the state become the items in the component's props
})

// Can be an object or a function. (Object recommended)
// These methods get access to 'dispatch'
// which is the only way to ssend signals to the store
const mapDispatchToProps = {
  deleteCar // this method gets passed into props and can then be called
}

// connect creates a HOC
const ConnectedComponent = connect(
  mapStateToProps,
  mapDispatchToProps
)(Component)

export default ConnectedComponent
export const deleteCar = (id) => ({
  type: 'DELETE_CAR',
  payload: {
    id,
  }
})

Action Creator

Component

Tools

DevTools Extensions

Resources

Testing React

How far can you take this?

Redux

By James Sherry

Redux

A brief introduction to flux methodology, focussing on Redux

  • 1,097