Attamatch

> Forked from Rematch for Attainia usage

Rethink Redux.

Rematch is Redux best practices without the boilerplate. No more action types, action creators, switch statements or thunks.

• Why we created Rematch
• Video: Introducing Rematch
• A comparison of Redux & Rematch

> See v0 stable docs. Currently only displaying experimental @next documentation.

> WARNING: Breaking changes with 1.0.0-beta.3. Global imports of dispatch and getState have been removed. See the Changelog for details.

Index

• Getting Started
• Purpose
• Examples
• Migration Guide
• API Reference
  • Core API
  • Init Redux API
  • Plugins API
• Recipes
  • Devtools
  • React
  • Vue
  • Testing
  • TypeScript
  • Immer
  • Decoupling reducers
• Plugins
  • Selectors
  • Loading
  • Persist
  • Updated
  • React Navigation
  • Immer
• Inspiration

Translations

• 中文手册

Getting Started

As we approach v1.0.0, the latest version of rematch and rematch plugins can be installed with the @next flag.

npm install attamatch

Step 1: Init

init configures your reducers, devtools & store.

index.js

import { init } from 'attamatch'
import * as models from './models'

const store = init({
  models,
})

export default store

For a more advanced setup, see plugins and Redux config options.

Step 2: Models

The model brings together state, reducers, async actions & action creators in one place.

models.js

export const count = {
  state: 0, // initial state
  reducers: {
    // handle state changes with pure functions
    increment(state, payload) {
      return state + payload
    }
  },
  effects: (dispatch) => ({
    // handle state changes with impure functions.
    // use async/await for async actions
    async incrementAsync(payload, rootState) {
      await new Promise(resolve => setTimeout(resolve, 1000))
      dispatch.count.increment(payload)
    }
  })
}

See the reducers docs to learn more, including how to trigger actions from other models.

Understanding models is as simple as answering a few questions:

1. What is my initial state? state
2. How do I change the state? reducers
3. How do I handle async actions? effects with async/await

Step 3: Dispatch

dispatch is how we trigger reducers & effects in your models. Dispatch standardizes your actions without the need for writing action types or action creators.

import { init } from 'attamatch'
import * as models from './models'

const store = init({
  models,
})

export const { dispatch } = store
                                                  // state = { count: 0 }
// reducers
dispatch({ type: 'count/increment', payload: 1 }) // state = { count: 1 }
dispatch.count.increment(1)                       // state = { count: 2 }

// effects
dispatch({ type: 'count/incrementAsync', payload: 1 }) // state = { count: 3 } after delay
dispatch.count.incrementAsync(1)                       // state = { count: 4 } after delay

Dispatch can be called directly, or with the dispatch[model][action](payload) shorthand.

Step 4: View

Rematch can be used with native redux integrations such as "react-redux". See an example below.

import React from 'react'
import ReactDOM from 'react-dom'
import { Provider, connect } from 'react-redux'
import store from './index'

const Count = props => (
  <div>
    The count is {props.count}
    <button>increment</button>
    <button>incrementAsync</button>
  </div>
)

const mapState = state =&gt; ({
  count: state.count
})

const mapDispatch = ({ count: { increment, incrementAsync }}) =&gt; ({
  increment: () =&gt; increment(1),
  incrementAsync: () =&gt; incrementAsync(1)
})

const CountContainer = connect(mapState, mapDispatch)(Count)

ReactDOM.render(
  
    
  ,
  document.getElementById('root')
)

Examples

• Count: JS | React | Vue | Angular
• Todos: React

Migrating From Redux

Moving from Redux to Rematch involves very few steps.

1. Setup Rematch init with Redux step 1
2. Mix reducers & models step 2
3. Shift to models step 3

API

See the attamatch API

Changelog

See the CHANGELOG to see what's new.

Like this project? ★ us on GitHub 😃