UNSAT lab about redux-thunk-lab

[kodyclemens]

@micahshute thanks for opening this issue with your explanation, it was very helpful.

[thekevinhuang]

I also agree with the above concerns. The language brought up in concern 1 had me very confused until I essentially chose to ignore it and figure it out on my own.

For concern 3, one pattern I found to be extremely nice when establishing a store structure is declaring it upfront as a const. Then when setting initial state you can set it equal to the const e.g.

`const initialState = {
loading : false,
pictures: []
}

function reducer (state=initialState, action) {
...
}`

This way it is clear what is expected and what the structure will be right from the get go. Including this info in the readme would have been tremendously helpful.

[maxwellbenton]

Hey @micahshute,

Thanks for this. I've updated this lab and the previous lesson to address some of these issues.

1. Because there isn't enough material on thunk and the previous example is just a readme, I've converted this lab to be much more guided and have rewritten it to go through the set up of redux and thunk. The expected actions and structure have changed, but most of the code is provided in the readme now, including the structure of actions and how the action creator should be written. There is also now a section that provides a bit more context to the purpose of LOADING_CATS.

2. mapStateToProps and mapDispatchToProps are now used in the code-along with a working code snippet example and a note that dispatch can still be called in App, even though we're now dispatching in the action creator.

3. Now that it is a code-along, the state structure is provided.

I believe these changes should resolve the issues brought up here, but if not, please feel free to reopen. Thanks again for the thorough feedback!