You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For tracking banner views and clicks I recently added this package to observe some of the FlatList components in our app. However everything seems to work fine, since I added the package I receive this warning in the console after some props are changing (e.g. after filtering):
Warning: PickerItem: key is not a prop. Trying to access it will result in undefined being returned. If you need to access the same value within the child component, you should pass it as a different prop. (https://reactjs.org/link/special-props)
I know the warning is triggered by another component inside IOFlatList, but I don't receive it when I replace IOFlatlist with FlatList. I found out the problem is the FilterSelect, which is in the ListHeaderComponent property, is remounted on each change using the IOFlatlist component. This isn't using the regular FlatList component.
Is there probably a way to prevent these components are remounted on every change using the IOFlatlist?
Hi,
For tracking banner views and clicks I recently added this package to observe some of the FlatList components in our app. However everything seems to work fine, since I added the package I receive this warning in the console after some props are changing (e.g. after filtering):
I know the warning is triggered by another component inside IOFlatList, but I don't receive it when I replace
IOFlatlist
withFlatList
. I found out the problem is theFilterSelect
, which is in theListHeaderComponent
property, is remounted on each change using the IOFlatlist component. This isn't using the regular FlatList component.Is there probably a way to prevent these components are remounted on every change using the IOFlatlist?
The FlatList component:
The filter component:
Thanks in advance!
Kind regard,
Geert van Soest
The text was updated successfully, but these errors were encountered: