Re-creating the entire body/row nodes on data change

I’m having an issue caused by this component re-creating the entire body when the data changes even though the scroll position is the same. I would think given this condition, React’s reconciliation algorithm would skip over the FixedSizeList Body/rows and just append the innerHtml of the cell with the new value (This would be the ideal for my useCase, but maybe not for everyones). If I generated a list by mapping over rows, if the data changed react would append the changes to the cell without destroying/re-creating everything.

I wonder if something could be done about this, I could even take a look at your src, but diving in would take some time to understand the internal flow.

[DDinenno]

Yep that did it.

I actually was memoizing the rows in my actual implementation, but I guess improperly since I was using Inline functions and not using the itemData( I didn’t think it was necessary at the time).

Great history lesson on inline-functions. I’m gonna stay away from those as much as possible.

Thanks a bunch! you don’t know how much this helped me out and sorry for wasting your time, it was mostly ignorance on my part. I took a look at your future changes and I’m hyped to see them in action. Good luck with everything, this is such a helpful plugin for react ecosystem!

[brunolemos]

I actually was memoizing the rows in my actual implementation, but I guess improperly since I was using Inline functions and not using the itemData( I didn’t think it was necessary at the time).

I just found out I did the exactly same thing, that’s why all list items were re-rendering even if only a single item changed. Thanks for pointing it out! 🙌