Closed yob closed 6 months ago
on custom emoji vs unicode ones, there's some discussion in #369. Maybe we want to allow the custom emoji to win and the only way for users to reach/use the new unicode ones is via the unicode codepoint. No :phoenix:
ascii option.
I followed the docs in
docs/updating-unicode.md
.We were already using emoji v15, so this is only a small bump. Mostly it's new modifiers to existing emojis, like "person walking facing right" (πΆββ‘οΈ)instead of the traditional "person walking [facing left]" (πΆ). There's a couple of new combinations that are visually distinctinve, like "lime" (πβπ©) made by combining "lemon" and "green" and "brown mushroom" (πβπ«) made by combining "mushroom" and "brown".
The above emojis are unlikely to work, I assume most systems won't have the glyphs in their emoji fonts yet. You can see the apple versions in this repo by by browsing to the README on this branch. eg:
The full list of new emojis is on emojopedia: https://emojipedia.org/emoji-15.1
One of the new emojis (phoenix) conflicts with the logo we add in 2016 (https://github.com/buildkite/emojis/pull/16) for the elixr framework.
It feels like it'd be nice to let users access both, but which one wins? This proposes we let the unicode emoji win, by moving the elixr framework icon to phoenix-elixr. This will be a visually breaking change for customers who use this emoji.