For instance when unicode adds a new block of emoji, or slack introduces new aliases.
Opting for json format would be a lot easier to maintain and we get a richer information like html and categories from this gist, or description and tags from this library.
I can think of 2 solutions:
Download the emoji.json as a resource, like this PR.
I included the emojis.json from emoji-java as a resource. However, I don't feel the need to add emoji-java as a dependency. We'll revisit the decision later if needed.
Maintaining the emoji.edn file could be hard.
Opting for json format would be a lot easier to maintain and we get a richer information like
html
andcategories
from this gist, ordescription
andtags
from this library.I can think of 2 solutions:
emoji-java
emoji-java
emoji-java
This is my thoughts so far. Any suggestion is welcome. The solution might be a combination of the two above.