reactjs-flux

My team is currently working on a large application being written in ReactJS using Facebook's Flux architecture. It is still in its infancy right now but it is going to grow big very soon. It will have more than 50 small component views, plenty of actions, stores and action-creators. Currently, our directory structure looks like - App |___ module_1 | |___ components | | |___ component1.react.js | | |___ component2.react.js | |___ module1ActionCreators.js | |___ module1Constants.js | |___ module1store.js | |___ module_2 |___ ... (same structure as above) One of the problems with this approach

While creating a component in Reactjs with input fields error occurs Error: Parse Error: Line 47: Expected corresponding JSX closing tag for input at http://localhost/chat-react/src/script.js:47:20 </div> var Main = React.createClass({ render: function() { return ( <div className="card-action"> <i class="mdi-action-account-circle prefix"></i> <input id="icon_prefix" type="text" class="validate"> </div> ); } }); You need to close the input element with a /> at the end. <input id="icon_prefix" type="text" class="validate" /> This error also happens if you have got the order of your components

I am using React + Flux. Our team is planning to move from flux to redux. Redux is very confusing for me coming from flux world. In flux control flow is simple from Components -> actions -> Store and store updates back components . Its simple and very clear. But in redux its confusing. There is no store here, yes there are some examples without using store. I went through several tutorials, it seems everyone has their own style of implementation. Some are using Containers and some are not. (I don't know this Containers concept and not able to understand what mapStateToProps, mapDispatchToProps

I just recently discovered Redux . It all looks good. Are there any downsides, gotcha or compromises of using Redux over Flux? Thanks Dan Abramov Redux author here! I'd like to say you're going to make the following compromises using it: You'll need to learn to avoid mutations. Flux is unopinionated about mutating data, but Redux doesn't like mutations and many packages complementary to Redux assume you never mutate the state. You can enforce this with dev-only packages like redux-immutable-state-invariant , use Immutable.js , or trust yourself and your team to write non-mutative code, but it

Thus far, the extent of my knowledge about how properties are passed from one component to another via parameters is as follows //start: extent of my knowledge Suppose there exists some state variable called topic in A.jsx. I want to pass this down to B.jsx, so I perform the following B = require('./B.jsx') getInitialState: function() {return {topic: "Weather"}} <B params = {this.state.topic}> In B.jsx I can then do stuff like module.exports = React.createClass({ render: function() { return <div><h2>Today's topic is {this.props.params}!</h2></div> } }) which when called upon will render "Today