Pause Component Rendering Till Data Fetch Completes about redux-thunk HOT 9 CLOSED

I was facing with the same issue... below is a solution that worked for me on the mapStateToProps
This will render an empty state while data you're waiting for is still undefined. it will prevent things from breaking while your component is rendering. The if clause will depend on what you're trying to receive. I am waiting for an array of object to return while the component is rendering

function mapStateToProps(state) {

if (state.activePlayer.length > 0) {
return {
activePlayer: state.activePlayer
}
} else {
return {};
}
}

from redux-thunk.

@mesmerize86 length refers to an array data type so if response is not an array, this will throw an error. You can try as a quick fix.
function mapStateToProp(state){

if(state.tweets.tweets.response){
....

from redux-thunk.

Have you tried placing this.props.fetchActivePlayer into your constructor?

In ES6 classes the constructor takes the place of componentWillMount.

see here https://babeljs.io/blog/2015/06/07/react-on-es6-plus

from redux-thunk.

Hi @Andriy-Kulak

I got an error length is not defined when I tried in my response. Just wondering if its the right way to do it?
function mapStateToProp(state){
if(state.tweets.tweets.response.length > 0){
return {
tweets : state.tweets.tweets
}
}else{
return {};
}
}

from redux-thunk.

BTW @lawrenceleach according to ES6 spec I think you can't use export default twice in a single js file

from redux-thunk.

same here, but I can't move initialization to constructor because I can't use "async" in constructor.
what I did to get rid of annoying "of undefined" is to use "*ngIf =(data) " to make sure all data is fetched completely before showing the component.

from redux-thunk.

@gaearon any recommendations to cleanly handle this situation? ie how to handle in your react components when data has not been done fetching. This problem might be caused by many things, components expecting data, or waiting for some data from an endpoint to comeback before triggering another call etc.

Thanks

from redux-thunk.

A possible fix could be to write a check directly in your action creator dispatch the action only when the fetch actually returns something.

return axios.get(${ROOT_URL}/players/${slug}) .then(response => { if(response){ dispatch({ type: FETCH_ACTIVE_PLAYER, payload: response }) } }) .catch(err => { console.error("Failure: ", err); }); }; }

Worked for me.

from redux-thunk.

@KO527 : This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out - you'll probably get a better answer faster. Thanks!

from redux-thunk.