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
I'm raising this as I was unable to find any issues answering this question.
I'm using Picker component. When user clicks, the emoji picker shows up in the UI.
I've not implemented any kind of lazy loading techniques to default Picker so I'm assuming it loads the emoji list during web app initial load phase or maybe it gets bundled during build. I'm not sure.
If I want to retrieve the list of emoji used by the Picker component, how do I achieve it ?
I don't want to install new package to get emoji list and I don't want to use CDN link to fetch new list when I know the Picker component was used elsewhere in the app and the emoji data is available to the app.
Thank you.
The text was updated successfully, but these errors were encountered:
If not initiated manually, data is indeed loaded from a CDN when you mount the picker for the first time. In order to use the data before mounting the component, you need to initialize the data manually. See example here: https://github.com/missive/emoji-mart#%EF%B8%8F%EF%B8%8F-headless-search. You can call init without any options, it will fetch the data on a CDN.
Hello,
I'm raising this as I was unable to find any issues answering this question.
I'm using Picker component. When user clicks, the emoji picker shows up in the UI.
I've not implemented any kind of lazy loading techniques to default Picker so I'm assuming it loads the emoji list during web app initial load phase or maybe it gets bundled during build. I'm not sure.
If I want to retrieve the list of emoji used by the Picker component, how do I achieve it ?
I don't want to install new package to get emoji list and I don't want to use CDN link to fetch new list when I know the Picker component was used elsewhere in the app and the emoji data is available to the app.
Thank you.
The text was updated successfully, but these errors were encountered: