I don't understand why you're reusing this variable. We should always avoid let if possible (though prefer let to using non-readonly types)

This is a really bad choice on where to inject the style change you want. Looking at createRecursiveDrawerItemsData, it appears that the primary purpose is to share the "depth-selection" logic between native and web. There's no reason that you need to apply your changes so far upstream, forcing yourself to handle things as a batch and with a .map call, as opposed to simply directly updating CommunityDrawerItem.

Separately, while investigating this I identified that we are using a nested FlatList-inside-FlatList approach here, which is bad for scroll behavior. @inka, can you create a follow-up task to address this, and link it here? (@ginsu, please make sure the task is created before landing this diff.)