Angular’s two-way data binding It’s made possible by a mechanism that synchronizes the view and the model whenever either change. In Angular, you update a variable and its change detection mechanism will take care of updating the view, and viceversa. What’s the problem? You don’t control the change detection mechanism. I found myself having to … Read more
I’ll let others do the compare/contrast with Angular, but here are some answers to two of your questions. So isn’t this actually MVC with a different name? The presence in Flux of a separation of concerns between the data/logic layer and the view layer does not make it MVC. Many other patterns have a similar … Read more
It looks like you’re on the right track. Just to make sure everyone’s on the same page for this answer, let’s get some terminology out of the way. Mock: A function with behavior controlled by the unit test. You usually swap out real functions on some object with a mock function to ensure that the … Read more
Is it correct/highly advisable to have all of my $.ajax calls inside my Web API Utils? Callbacks call the action creators, passing the data in the process. Yes, you should put all your request into a single entity, i.e. the Web API Utils. They should dispatch the responses so any store can choose to act … Read more
Flux is an architect pattern to build React application. So you can use Backbone models and collections inside your stores to fetch and store data. And if want to use just React’s Virtual DOM feature, there is no need to use react.js. There are a lot of libraries, adding Virtual DOM feature to your application … Read more
So my final conclusion on this question is that I didn’t think it through properly. It seemed natural just to pass my data through the Link so I can access them in my Child component. As Colin Ramsay mentioned there is something called state in the Link but that’s not the way to do it. … Read more
[Update] After working on a bunch of React/flux applications, I’ve come to the conclusion that I prefer for routing to be handled separately and orthogonally to flux. The strategy is that the URL/routes should determine which components get mounted, and the components request data from the stores based on the route parameters and other application … Read more
Ideally, never! If your Flux stores are using Immutable.js then try to maintain all the way through. Use React.addons.ReactComponentWithPureRenderMixin to achieve a memoization performance win (it adds a shouldComponentUpdate methods). When rendering, you may need to call toJS() as React v0.12.x only accepts Array as children: render: function () { return ( <div> {this.props.myImmutable.map(function (item) … Read more
In the official examples we have several top-level directories: components for “dumb” React components unaware of Redux; containers for “smart” React components connected to Redux; actions for all action creators, where file name corresponds to part of the app; reducers for all reducers, where file name corresponds to state key; store for store initialization. This … Read more
Definitely persist the state of your reducers! If you persisted a sequence of actions instead, you wouldn’t ever be able to modify your actions in your frontend without fiddling around inside your prod database. Example: persist one reducer’s state to a server We’ll start with three extra action types: // actions: ‘SAVE’, ‘SAVE_SUCCESS’, ‘SAVE_ERROR’ I … Read more