write :smile: for 😄, :tada: for 🎉, :rocket: for 🚀 #540

[pdurbin]

Pull Request Checklist

• I have linked this PR to related GitHub issue.
• I have updated the CHANGELOG.md file with relevant changes (the file is located at the root of monorepo).

This is just a draft pull request for now. @holmesworcester and I were talking about it.

It's for this issue:

• User should be able to write :smile: for 😄 and use other emoji codes #540

So far I'm only supporting three emoji codes (smile, tada, and rocket). And there's no preview, no picker. I was just happy to get something working. 😅

Here are a couple screenshots:

[holmesworcester]

Looks great! I think if we had a complete emojimap and a couple tests this would be good to go.

[pdurbin]

Ha. Thanks. Just hacking for fun. 😜

For the complete emojimap, we should probably tap in to our existing emoji library, right? It looks like @siepra added https://www.npmjs.com/package/emoji-picker-react in 654b315. I see the data I want over at https://github.com/ealush/emoji-picker-react/blob/4.0.0/src/data/emojis.json for example. In GitHub I type :sweat_smile: to get 😅 and that JSON file has pretty much the same, but with spaces instead of underscores and no colons...

{
  "n": [
    "sweat smile",
    "smiling face with open mouth and cold sweat"
  ],
  "u": "1f605",
  "a": "0.6"
},

... but we can probably work with that. From the emoji-picker-react docs I'm not sure how to get at the data. I'm not sure where to pass in sweat smile to get the emoji I want, I mean. This issue suggests that maybe the data needs to be exported:

• Export emoji data ealush/emoji-picker-react#349

Does that sound right?

Also, where should I add tests, please?

Finally, two tests are failing in this PR:

• Check / check (ubuntu-20.04) (pull_request)
• Visual regressions / chromatic-deployment (ubuntu-20.04) (pull_request)

Is this expected for outside contributors? Thanks!

[holmesworcester]

I would be okay with duplicating the data by hand if that's the best solution.

Another thing we could do is look at how matternost solves this problem. There might be another library that is useful.

[pdurbin]

I'm not actively working on this so I'm going to close this pull request to reduce noise and clutter. Maybe a future developer and at least see which files need to be touched by looking at it.