3 ms·
No, this isn't a React render issue (and React render in general doesn't have this issue. Put a `key` on your component and everything will work correctly). If
by chenglou 12y ago
No, this isn't a React render issue (and React render in general doesn't have this issue. Put a `key` on your component and everything will work correctly). If the item isn't changed then its DOM representation isn't touched either, so neither is the CSS recalculated.
He can freely render as many times as he wants (a dozen function calls won't be your bottleneck); I'd even argue it _could_ be nicer that everything's rendered gradually this way, but that's just an aesthetic choice.
- insin 12y agoThis was just the most simple way to get started. I was surprised the result wasn't _completely_ terrible :) Every individual item uses a ReactFireMixin method to register its own Firebase reference, binding the incoming data as an object in its state, so they pop in as the websocket receives data, then auto-update every time new data arrives.