Wednesday, November 28, 2018

javascript - React + Flux: Getting initial state into a store



We have recently switched over to React + Flux from Angular to build a rather complex business application.




Taking the approach of having one container component that passes all state as properties down the component tree isn't a practical way to develop the app for us as the app makes use of large page-like modals. Enough state does get passed down to the modals for them to load their data into their stores.



The problem I have is I need to get some initial state (passed down as props) into the modal component's store. In this post the good guys over at Facebook say it's ok to use props for initial state when synchronization is not the goal.



This is how I get the initial state into my store currently:



var ABC = React.createClass({
...
getInitialState: function() {

return ABCStore.getInitialABCState(this.props.initialA);
},
...

var ABCStore = Reflux.createStore({
...
init: function() {
_state = {
a: null,
b: 'B init',

c: 'C init'
};
},

getInitialABCState: function(initialA) {
_state.a = initialA;
return _state;
},

getABCState: function() {

return _state;
}
...


I am unsure what the best practice is to do this, or whether this is a Flux anti-pattern?


Answer



It feels wrong to me that you are using getInitialState() to change the state of your store. You should at least be doing that in componentWillMount.



I would trigger an action in componentWillMount and have the store handler update the internal state of the store (this should always be the case in flux). Then your component's change handler for the store can consume whatever data that you are currently calling your "initial state"



No comments:

Post a Comment

plot explanation - Why did Peaches' mom hang on the tree? - Movies & TV

In the middle of the movie Ice Age: Continental Drift Peaches' mom asked Peaches to go to sleep. Then, she hung on the tree. This parti...