How re-rendering should be done in efficient way while data change in flux architecture controller?

[tsfahmad]

I have a controller which consist of many views in it. Only my controller is having state and I pass data to my views through props. Now problem is suppose my view depends on number of product.
Say we have more than 100 products and each product consist of number of properties related to it. Now each property also have their own property on it. So if I change value of a sub-property then i have to re-render. No We dispatch the change event so it again start re-rendering from controller and it have to process through all the codes like all condition checks, loops etc which is time consuming. So how should we achieve it flux-react architecture?

[andersekdahl]

If you're concerned about performance of rerendering and diffing, you might want to look into Immutable.js and shouldComponentUpdate. It makes it possible to skip rerendering components for which the data hasn't changed.

[jimfb]

In the future, we might be able to do something like this: #3920 or #3398 (both options still in discussion, feel free to let us know which you like better!)

[zpao]

I'm going to close this out since it's an architectural question. Check out other issues and consider discussing this on stack overflow or the discussion boards (discuss.reactjs.com)