khriztianmoreno.com
@khriztianmoreno
I'm a community leader and altruistic speaker.
FullStack Javascript Developer
<Commit.fm /> Podcast
https://spoti.fi/2EfgTlu
Youtube
https://bit.ly/2GNFgbH
Senior Frontend Developer
@khriztianmoreno
@khriztianmoreno
- Create action with type and payload
- Returns a formatted action object
(Telegraph operator)
// FSA
{
type: 'TYPE',
payload: {},
error: false,
meta: {}
}@khriztianmoreno
- There is only one
- It takes care of holding on to the whole state tree
- It delegates the work of figuring out what state changes need to happen
(over-controlling bureaucrats)
@khriztianmoreno
- When the store needs to know how an action changes the state, it asks the reducers.
- The state object isn’t manipulated directly.
- Each slice is copied and then all of the slices are combined into a new state object.
(department of white-collar workers)
@khriztianmoreno
More info in other slides:
@khriztianmoreno
The redux-actions library offers a small but powerful API to help cut down on some of the
Methods
createAction(s), handleAction(s), combineActions
@khriztianmoreno
@khriztianmoreno
By Khriztian Moreno
Redux is a powerful way to manage application state, but that power can come with a lot of code. A single update can sometimes require changes across many files and the code required to define action creators and to handle those actions in your reducer can start to get pretty repetitive. The redux-actions library offers a small but powerful API to help cut down on some of the boilerplate that is typical of an application that uses Redux to handle state management.
