React-Redux-Workflow

A place for me to keep notes on setting up redux in a react project reference: http://redux.js.org/docs/api/createStore.html the repo I’m working on which this note refers to: https://github.com/cici-chen/Fifty-Shades-Of-Pink/tree/refactor for workflow logic: https://quickleft.com/blog/redux-plain-english-workflow/

Install node modules

npm i --save-dev redux react-redux redux-thunk

Create Store

To keep index.js in root/client pristine, we are creating a store file then import it into index.js, but we could have just added it in index.js

in root/client/store.js ``` import {createStore, applyMiddleware, compose} from ‘redux’ //There should only be a single store in your app //{compose} is used to apply several store enhancers in a row import thunkMiddleware from ‘redux-thunk’

import reducers from ‘./reducers’

export default function store = createStore(reducers, compose( applyMiddleware(thunkMiddleware), window.devToolsExtension ? window.devToolsExtension() : f => f ))

### Link Store to our app
> in root/client/index.js

import {Provider} from ‘react-redux’ //Makes the Redux store available to the connect() calls in the component wrapped in them. import store from ‘./store’

Then in the part where you render your <App/>

document.addEventListener(‘DOMContentLoaded’, () => { ReactDOM.render( <Provider store={store}> </Provider>, document.getElementById(‘app’) ) })

I wanna see the state of the store, so I added this in the file too

console.log(‘State of the entire app’, store.getState())

### Make a component smart
copied from: https://quickleft.com/blog/redux-plain-english-workflow/
The notion is pretty straight-forward: if you want to wisen up your component, use the connect method from react-redux. Connecting your component gives it access to the global state object. It’s highly unlikely however, that our component needs access to everything in the state object. We can slice off only what we want the component to be aware of in the mapStateToProps function. The global state object will have various other keys in it, but in the example below, we’re only allowing questions through.

Create a container for the component & import the component in it

> in root/Client/Containers/StoryLibrary.js

import React from ‘react’ import { connect } from ‘react-redux’;

import StoryLibrary from ‘../components/StoryLibrary.jsx’

const StoryLibrary = (props) => (

)

function mapStateToProps(state) { return { stories: state.stories }; }

export default connect(mapStateToProps)(StoryLibrary)

### Dispatch an action
Within the QuestionsPage component, we can use one of React’s component callbacks (i.e. componentWillMount) to initiate the fetching of questions. All smart components have access to the dispatch method via props.  The dispatch method allows us to execute an action creator, perform logic, and ultimately update the global state object.
> in root/client/containers/StoryLibrary.js

import { fetchStories } from ‘../actions’

const StoryLibrary = (props) => ( … componentWillMount(){ props.dispatch(fetchStories()) } … );

### Write the action creater
> in root/client/actions/index.js

import {getStories} from ‘../api/stories’

export function fetchStories(){ return getStories() }

export function receiveStories(stories){ return{ type:’RECEIVE_STORIES’, stories } }

### Prepare data for the reducer
- set up api functions and so on

### Test redux
reference:http://redux.js.org/docs/recipes/WritingTests.html
1. Install Jest testing engine
To use it together with Babel, you will need to install babel-jest:

npm install –save-dev jest babel-jest

2. Configure in package.json
> in root/package.json
Make sure you have

“babel”: { “presets”: [ “es2015”, “react” ] },

Mine already had es2015 and react set up in it, not sure when did that happen.
Add test scrtipt too

“scripts”: { “test-jest”: “jest’tests/redux/*.test.js’”, “test:watch”: “npm test – –watch” ```

and run npm run test-jest to run it once, or npm run test:watch to test on every file change.

Test Async Action Creators

For async action creators using Redux Thunk or other middleware, it’s best to completely mock the Redux store for tests. You can apply the middleware to a mock store using redux-mock-store. You can also use nock to mock the HTTP requests.

I spent an entire afternoon trying to make it work but it just didn’t so I gave up. At first my test failed because my api function was returning a callback instead of promise, and jest just couldn’t handle it. Then my test failed because it didn’t like that my api address was a non-absolute url. I think I became overly obsessed with tests and missed the point of it and really wasted heaps of time. I should have time boxed this shit.

Write reducer to build the final state object