-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emoji Mart: Update to Emoji 15 #24
Changes from all commits
f86ccb3
c8814af
d1b6f5f
fcfa180
c22a82a
a755469
58ddd98
f142052
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,7 +16,7 @@ describe('Data', () => { | |
|
||
test('emojis', () => { | ||
expect(Data).toHaveProperty('emojis') | ||
expect(Object.keys(Data.emojis).length).toBe(1849) | ||
expect(Object.keys(Data.emojis).length).toBe(1870) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. interesting I thought the new emoji count would be higher! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, small update: https://emojipedia.org/emoji-15.0 |
||
for (const emojiId of Object.keys(Data.emojis)) { | ||
const emoji = Data.emojis[emojiId] | ||
expect(emoji).toHaveProperty('id') | ||
|
@@ -34,7 +34,5 @@ describe('Data', () => { | |
test('alias', () => { | ||
expect(Data).toHaveProperty('aliases') | ||
expect(Data.aliases['satisfied']).toBe('laughing') | ||
expect(Data.aliases['beetle']).toBe('ladybug') | ||
expect(Data.aliases['man_in_tuxedo']).toBe('person_in_tuxedo') | ||
}) | ||
}) |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,6 +25,6 @@ export default class PickerElement extends ShadowElement { | |
} | ||
} | ||
|
||
if ('customElements' in window && !customElements.get('em-emoji-picker')) { | ||
customElements.define('em-emoji-picker', PickerElement) | ||
if ('customElements' in window && !customElements.get('em-emoji-picker-15')) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This was a wonky quirk. Basically, this There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Will you have two entries in Figma's package.json pointing to two different shas? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
customElements.define('em-emoji-picker-15', PickerElement) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have the time, can you elaborate why this is safe to remove? I can't quite infer what the original issue was (and why updating emoji sets fixes it) looking at the comment getting ripped out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the before times (6+ years ago), we special-cased these 2 emoji. As part of the emoji 14 upgrade, we got the product go-ahead to stop special-casing them. I think it was before the
ladybug
emoji was introduced. I had stripped out all of those use cases from our code except for this one (see the last subtask here: https://app.asana.com/0/1204728196943613/1205011813641107/f). I had deprioritized it, but since I was in here anyways figured I may as well remove it.So this is a (small) change in user experience, but an intentional green-lit one.