Peter Piekarczyk comments

Results 112 comments of


                                            Peter Piekarczyk

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

Hey this is really great! I'm just getting my feet wet with this library, but I'm going to apply what you have here to my own project and see if...

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

Hey @anyong! The `initialState` that you define in your reducer, does that play the same role `combineReducers` would? Is that where you're going with that? Are you explicitly listing all...

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

Thanks for the quick reply! Gotcha. Just so I understand, it looks like you're getting rid of having to use `combineReducers` because everything is handled within the api reducer, right?...

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

Hey @anyong Just wanted to let you know this all makes sense. I took a look through the real-world example and could match the ideas. Thank you for helping me...

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

Hey @anyong , After playing around with this for a few days. Here are some pain points: CRUD. This technique seems to be working great when you only have to...

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

Ok, sorry for the lack of context. Did a ton of refactoring on my end. For anyone else interested, this can DEFINITELY be cleaned up, but I just needed something...

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

@janjon - create api/xhr.js file, paste this in there - within your async action creators, call api - create an api reducer that handles API_SUCCESS,FAILURE,REQUEST, etc. :)

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

So this was an edge case I was dealing with. The server would sometimes respond with a keyed payload and sometimes it would return the payload: ``` customers: { name:...

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

you will have to write your own call-api middleware for that unless this middleware supports it. It's relatively easy and http://redux.js.org/ actually has one for you to use :)

API calls that dispatch multiple actions for keeping API response data and other stuff (like metadata, etc.) in separate parts of the store? (With sample code)

@Gamemaniak whether you write your own custom api middleware or use this one, you can return a promise. I'm not sure what you mean by listening for a promise