Closed benjaminben closed 6 years ago
This seems to indicate that key
should force fresh creation of the component https://discuss.reactjs.org/t/how-does-react-decide-whether-to-reuse-an-existing-component/571 but again I'm not totally sure how the implementation works re: flatlist
Word only rendering the current and next appears to be working great 👍
This is probably the dumbest way I could imagine doing this, rendering a
<RecView/>
for every single rec in our entire db dump. BUT it does allow us to animate between recs which is chill, and it solves our scroll index reset problem on the<FlatList/>
. Lmk what you suggest to improve, I wouldn't exactly consider this merge-ready.Also some noise related to the new build I archived this morning.