Custom Emojis as a changing prop

[vcervellera-turbulent]

👋

Encountered issue:
We provide the picker with custom emojis based on different contexts, which means that in certain circumstances, the picker has custom emojis that will not be present at the next opening.
However, the CUSTOM_CATEGORY emojis array is built outside of the Picker class, and is kept in memory for all uses of the Picker, and therefore keeps any emojis its provided in memory, even when the Picker receives an empty custom prop in the future.

Fix:
Upon construction of the Picker, as we check if the custom prop has no length, I check if the CUSTOM_CATEGORY object contains emojis with a length, and reset it if so, to avoid contamination.

[savardc]

Hi @EtienneLem, just making sure you haven't missed this fix. Understand if you're busy. Thanks!

[EtienneLem]

@savardc Oh, thanks for the reminder.
@vcervellera-turbulent Thanks for the PR 🤘

[EtienneLem]

As a FYI: I noticed that we had other issues (#166) caused by the same thing. So although I did merge the PR, I sorta reverted it in the next commit (fed9a89) as it wasn’t required anymore.

These constants are now defined on each instance, instead of being shared. 😄

[vishalDhull0910]

hey @vcervellera-turbulent can you please help me out here ,facing similar issue

how to reset react picker