Is it imperative that there are no keys within the hierarchy of renderItem?

[miikemccabe]

I'm looking into using FlashList instead of FlatList. Things were working except when scrolling down quickly the images for some items were wrong and then the correct one would pop in. Adding a key to the image fixed this issue.

The docs say

Make sure your item components and their nested components don't have a key prop. Using this prop will lead to FlashList not being able to recycle views, losing all the benefits of using it over FlatList.

Does adding a key to any child of the rendered item really result in the use of FlashList being pointless?

If so I'm not sure I can use FlashList because it would be so easy for someone in the future to add a child component with a key somewhere in the hierarchy and destroy the performance benefits without even knowing.