2020-07-29 21:20:41 +02:00
|
|
|
import _ from "lodash";
|
|
|
|
|
2020-07-25 23:59:49 +02:00
|
|
|
// We will get actual values when we get initialized.
|
|
|
|
let emoji_codes = {};
|
|
|
|
|
2018-07-20 13:43:22 +02:00
|
|
|
// `emojis_by_name` is the central data source that is supposed to be
|
2021-05-14 00:16:30 +02:00
|
|
|
// used by every widget in the web app for gathering data for displaying
|
2018-07-20 13:43:22 +02:00
|
|
|
// emojis. Emoji picker uses this data to derive data for its own use.
|
2022-03-25 16:11:27 +01:00
|
|
|
export let emojis_by_name = new Map();
|
2018-07-20 13:43:22 +02:00
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
export const all_realm_emojis = new Map();
|
|
|
|
export const active_realm_emojis = new Map();
|
2021-11-19 13:49:00 +01:00
|
|
|
export const deactivated_emoji_name_to_code = new Map();
|
2020-07-25 01:02:07 +02:00
|
|
|
|
2022-03-25 17:52:12 +01:00
|
|
|
let default_emoji_aliases = new Map();
|
2013-07-02 00:40:57 +02:00
|
|
|
|
2020-07-24 00:39:22 +02:00
|
|
|
// For legacy reasons we track server_realm_emoji_data,
|
|
|
|
// since our settings code builds off that format. We
|
|
|
|
// should move it to use all_realm_emojis, which requires
|
|
|
|
// adding author_id here and then changing the settings code
|
|
|
|
// in a slightly non-trivial way.
|
2020-07-25 01:02:07 +02:00
|
|
|
let server_realm_emoji_data = {};
|
2020-07-24 00:39:22 +02:00
|
|
|
|
|
|
|
// We really want to deprecate this, too.
|
2020-07-25 00:12:17 +02:00
|
|
|
export function get_server_realm_emoji_data() {
|
|
|
|
return server_realm_emoji_data;
|
|
|
|
}
|
2020-07-24 00:39:22 +02:00
|
|
|
|
2020-07-25 23:59:49 +02:00
|
|
|
let emoticon_translations = [];
|
|
|
|
|
2022-03-25 15:22:37 +01:00
|
|
|
function build_emoticon_translations({emoticon_conversions}) {
|
markdown: Build the emoticon regexes up front.
There are six emoticon regexes that allow us
make translations such as ":)" to ":slight_smile".
We now build these as soon as we read in the
JSON data, instead of rebuilding them every time
we convert a message to markdown.
It's possible that we should just hardcode this
data:
[
{ regex: /(\:\))/g, replacement_text: ':slight_smile:' },
{ regex: /(\(\:)/g, replacement_text: ':slight_smile:' },
{ regex: /(\:\/)/g, replacement_text: ':confused:' },
{ regex: /(<3)/g, replacement_text: ':heart:' },
{ regex: /(\:\()/g, replacement_text: ':frown:' },
{ regex: /(\:\|)/g, replacement_text: ':expressionless:' }
]
OTOH I suppose it's possible that some server
admins will want to modify emoji_codes.json to
have custom emoticons.
2020-02-15 14:20:22 +01:00
|
|
|
/*
|
|
|
|
|
2022-03-25 15:22:37 +01:00
|
|
|
Please keep this as a pure function so that we can
|
|
|
|
eventually share this code with the mobile codebase.
|
|
|
|
|
markdown: Build the emoticon regexes up front.
There are six emoticon regexes that allow us
make translations such as ":)" to ":slight_smile".
We now build these as soon as we read in the
JSON data, instead of rebuilding them every time
we convert a message to markdown.
It's possible that we should just hardcode this
data:
[
{ regex: /(\:\))/g, replacement_text: ':slight_smile:' },
{ regex: /(\(\:)/g, replacement_text: ':slight_smile:' },
{ regex: /(\:\/)/g, replacement_text: ':confused:' },
{ regex: /(<3)/g, replacement_text: ':heart:' },
{ regex: /(\:\()/g, replacement_text: ':frown:' },
{ regex: /(\:\|)/g, replacement_text: ':expressionless:' }
]
OTOH I suppose it's possible that some server
admins will want to modify emoji_codes.json to
have custom emoticons.
2020-02-15 14:20:22 +01:00
|
|
|
Build a data structure that looks like something
|
|
|
|
like this:
|
|
|
|
|
|
|
|
[
|
2020-06-30 21:16:29 +02:00
|
|
|
{ regex: /(\:\))/g, replacement_text: ':smile:' },
|
|
|
|
{ regex: /(\(\:)/g, replacement_text: ':smile:' },
|
markdown: Build the emoticon regexes up front.
There are six emoticon regexes that allow us
make translations such as ":)" to ":slight_smile".
We now build these as soon as we read in the
JSON data, instead of rebuilding them every time
we convert a message to markdown.
It's possible that we should just hardcode this
data:
[
{ regex: /(\:\))/g, replacement_text: ':slight_smile:' },
{ regex: /(\(\:)/g, replacement_text: ':slight_smile:' },
{ regex: /(\:\/)/g, replacement_text: ':confused:' },
{ regex: /(<3)/g, replacement_text: ':heart:' },
{ regex: /(\:\()/g, replacement_text: ':frown:' },
{ regex: /(\:\|)/g, replacement_text: ':expressionless:' }
]
OTOH I suppose it's possible that some server
admins will want to modify emoji_codes.json to
have custom emoticons.
2020-02-15 14:20:22 +01:00
|
|
|
{ regex: /(\:\/)/g, replacement_text: ':confused:' },
|
|
|
|
{ regex: /(<3)/g, replacement_text: ':heart:' },
|
|
|
|
{ regex: /(\:\()/g, replacement_text: ':frown:' },
|
2021-03-04 19:25:59 +01:00
|
|
|
{ regex: /(\:\|)/g, replacement_text: ':expressionless:' },
|
|
|
|
....
|
markdown: Build the emoticon regexes up front.
There are six emoticon regexes that allow us
make translations such as ":)" to ":slight_smile".
We now build these as soon as we read in the
JSON data, instead of rebuilding them every time
we convert a message to markdown.
It's possible that we should just hardcode this
data:
[
{ regex: /(\:\))/g, replacement_text: ':slight_smile:' },
{ regex: /(\(\:)/g, replacement_text: ':slight_smile:' },
{ regex: /(\:\/)/g, replacement_text: ':confused:' },
{ regex: /(<3)/g, replacement_text: ':heart:' },
{ regex: /(\:\()/g, replacement_text: ':frown:' },
{ regex: /(\:\|)/g, replacement_text: ':expressionless:' }
]
OTOH I suppose it's possible that some server
admins will want to modify emoji_codes.json to
have custom emoticons.
2020-02-15 14:20:22 +01:00
|
|
|
]
|
|
|
|
|
2021-07-28 16:00:58 +02:00
|
|
|
We build up this list of ~12 emoticon translations even
|
|
|
|
if user_settings.translate_emoticons is false, since
|
markdown: Build the emoticon regexes up front.
There are six emoticon regexes that allow us
make translations such as ":)" to ":slight_smile".
We now build these as soon as we read in the
JSON data, instead of rebuilding them every time
we convert a message to markdown.
It's possible that we should just hardcode this
data:
[
{ regex: /(\:\))/g, replacement_text: ':slight_smile:' },
{ regex: /(\(\:)/g, replacement_text: ':slight_smile:' },
{ regex: /(\:\/)/g, replacement_text: ':confused:' },
{ regex: /(<3)/g, replacement_text: ':heart:' },
{ regex: /(\:\()/g, replacement_text: ':frown:' },
{ regex: /(\:\|)/g, replacement_text: ':expressionless:' }
]
OTOH I suppose it's possible that some server
admins will want to modify emoji_codes.json to
have custom emoticons.
2020-02-15 14:20:22 +01:00
|
|
|
that setting can be flipped via live update events.
|
|
|
|
On the other hand, we assume that emoticon_conversions
|
|
|
|
won't change until the next reload, which is fine for
|
|
|
|
now (and we want to avoid creating new regexes on
|
|
|
|
every new message).
|
|
|
|
*/
|
|
|
|
|
|
|
|
const translations = [];
|
2022-03-25 15:22:37 +01:00
|
|
|
for (const [emoticon, replacement_text] of Object.entries(emoticon_conversions)) {
|
2020-07-29 21:20:41 +02:00
|
|
|
const regex = new RegExp("(" + _.escapeRegExp(emoticon) + ")", "g");
|
2020-05-27 04:17:29 +02:00
|
|
|
|
|
|
|
translations.push({
|
2020-07-20 22:18:43 +02:00
|
|
|
regex,
|
|
|
|
replacement_text,
|
2020-05-27 04:17:29 +02:00
|
|
|
});
|
markdown: Build the emoticon regexes up front.
There are six emoticon regexes that allow us
make translations such as ":)" to ":slight_smile".
We now build these as soon as we read in the
JSON data, instead of rebuilding them every time
we convert a message to markdown.
It's possible that we should just hardcode this
data:
[
{ regex: /(\:\))/g, replacement_text: ':slight_smile:' },
{ regex: /(\(\:)/g, replacement_text: ':slight_smile:' },
{ regex: /(\:\/)/g, replacement_text: ':confused:' },
{ regex: /(<3)/g, replacement_text: ':heart:' },
{ regex: /(\:\()/g, replacement_text: ':frown:' },
{ regex: /(\:\|)/g, replacement_text: ':expressionless:' }
]
OTOH I suppose it's possible that some server
admins will want to modify emoji_codes.json to
have custom emoticons.
2020-02-15 14:20:22 +01:00
|
|
|
}
|
|
|
|
|
2022-03-25 15:22:37 +01:00
|
|
|
return translations;
|
2020-07-25 23:59:49 +02:00
|
|
|
}
|
markdown: Build the emoticon regexes up front.
There are six emoticon regexes that allow us
make translations such as ":)" to ":slight_smile".
We now build these as soon as we read in the
JSON data, instead of rebuilding them every time
we convert a message to markdown.
It's possible that we should just hardcode this
data:
[
{ regex: /(\:\))/g, replacement_text: ':slight_smile:' },
{ regex: /(\(\:)/g, replacement_text: ':slight_smile:' },
{ regex: /(\:\/)/g, replacement_text: ':confused:' },
{ regex: /(<3)/g, replacement_text: ':heart:' },
{ regex: /(\:\()/g, replacement_text: ':frown:' },
{ regex: /(\:\|)/g, replacement_text: ':expressionless:' }
]
OTOH I suppose it's possible that some server
admins will want to modify emoji_codes.json to
have custom emoticons.
2020-02-15 14:20:22 +01:00
|
|
|
|
2019-11-02 00:06:25 +01:00
|
|
|
const zulip_emoji = {
|
2020-07-15 01:29:15 +02:00
|
|
|
id: "zulip",
|
|
|
|
emoji_name: "zulip",
|
2023-02-02 21:22:40 +01:00
|
|
|
// We don't use a webpack'd URL here, for consistency with the
|
|
|
|
// server-side markdown, which doesn't want to render it into the
|
|
|
|
// message content.
|
2020-07-15 01:29:15 +02:00
|
|
|
emoji_url: "/static/generated/emoji/images/emoji/unicode/zulip.png",
|
2017-05-01 01:13:28 +02:00
|
|
|
is_realm_emoji: true,
|
2017-06-20 22:50:55 +02:00
|
|
|
deactivated: false,
|
2017-05-01 01:13:28 +02:00
|
|
|
};
|
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
export function get_emoji_name(codepoint) {
|
2020-02-15 13:19:42 +01:00
|
|
|
// get_emoji_name('1f384') === 'holiday_tree'
|
2022-01-24 08:23:22 +01:00
|
|
|
if (Object.hasOwn(emoji_codes.codepoint_to_name, codepoint)) {
|
2020-05-27 04:17:29 +02:00
|
|
|
return emoji_codes.codepoint_to_name[codepoint];
|
|
|
|
}
|
2020-09-24 07:50:36 +02:00
|
|
|
return undefined;
|
2020-07-25 00:12:17 +02:00
|
|
|
}
|
2020-02-15 13:19:42 +01:00
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
export function get_emoji_codepoint(emoji_name) {
|
2020-02-15 13:19:42 +01:00
|
|
|
// get_emoji_codepoint('avocado') === '1f951'
|
2022-01-24 08:23:22 +01:00
|
|
|
if (Object.hasOwn(emoji_codes.name_to_codepoint, emoji_name)) {
|
2020-05-27 04:17:29 +02:00
|
|
|
return emoji_codes.name_to_codepoint[emoji_name];
|
|
|
|
}
|
2020-09-24 07:50:36 +02:00
|
|
|
return undefined;
|
2020-07-25 00:12:17 +02:00
|
|
|
}
|
2020-02-15 13:19:42 +01:00
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
export function get_realm_emoji_url(emoji_name) {
|
2020-02-15 13:19:42 +01:00
|
|
|
// If the emoji name is a realm emoji, returns the URL for it.
|
2020-10-23 02:43:28 +02:00
|
|
|
// Returns undefined for Unicode emoji.
|
2020-02-15 13:19:42 +01:00
|
|
|
// get_realm_emoji_url('shrug') === '/user_avatars/2/emoji/images/31.png'
|
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
const data = active_realm_emojis.get(emoji_name);
|
2020-02-15 13:19:42 +01:00
|
|
|
|
|
|
|
if (!data) {
|
2020-10-23 02:43:28 +02:00
|
|
|
// Not all emojis have URLs, plus the user
|
2020-02-15 13:19:42 +01:00
|
|
|
// may have hand-typed an invalid emoji.
|
|
|
|
// The caller can check the result for falsiness
|
|
|
|
// and then try alternate ways of parsing the
|
2020-08-11 01:47:49 +02:00
|
|
|
// emoji (in the case of Markdown) or just do
|
2020-02-15 13:19:42 +01:00
|
|
|
// whatever makes sense for the caller.
|
2020-09-24 07:50:36 +02:00
|
|
|
return undefined;
|
2020-02-15 13:19:42 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
return data.emoji_url;
|
2020-07-25 00:12:17 +02:00
|
|
|
}
|
2020-02-15 13:19:42 +01:00
|
|
|
|
2022-03-25 16:11:27 +01:00
|
|
|
function build_emojis_by_name({
|
|
|
|
realm_emojis,
|
|
|
|
emoji_catalog,
|
|
|
|
get_emoji_name,
|
|
|
|
default_emoji_aliases,
|
|
|
|
}) {
|
|
|
|
// Please keep this as a pure function so that we can
|
|
|
|
// eventually share this code with the mobile codebase.
|
|
|
|
const map = new Map();
|
2020-07-25 02:24:01 +02:00
|
|
|
|
2022-03-25 16:11:27 +01:00
|
|
|
for (const codepoints of Object.values(emoji_catalog)) {
|
2020-07-25 02:24:01 +02:00
|
|
|
for (const codepoint of codepoints) {
|
2020-07-25 00:12:17 +02:00
|
|
|
const emoji_name = get_emoji_name(codepoint);
|
2022-03-29 15:06:03 +02:00
|
|
|
if (emoji_name !== undefined) {
|
2020-07-25 02:24:01 +02:00
|
|
|
const emoji_dict = {
|
|
|
|
name: emoji_name,
|
|
|
|
display_name: emoji_name,
|
|
|
|
aliases: default_emoji_aliases.get(codepoint),
|
|
|
|
is_realm_emoji: false,
|
|
|
|
emoji_code: codepoint,
|
|
|
|
has_reacted: false,
|
|
|
|
};
|
2022-03-29 15:06:03 +02:00
|
|
|
// We may later get overridden by a realm emoji.
|
2022-03-25 16:11:27 +01:00
|
|
|
map.set(emoji_name, emoji_dict);
|
2020-07-25 02:24:01 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2022-03-25 16:11:27 +01:00
|
|
|
|
2022-03-29 15:06:03 +02:00
|
|
|
for (const [realm_emoji_name, realm_emoji] of realm_emojis) {
|
|
|
|
const emoji_dict = {
|
|
|
|
name: realm_emoji_name,
|
|
|
|
display_name: realm_emoji_name,
|
|
|
|
aliases: [realm_emoji_name],
|
|
|
|
is_realm_emoji: true,
|
|
|
|
url: realm_emoji.emoji_url,
|
|
|
|
has_reacted: false,
|
|
|
|
};
|
|
|
|
|
|
|
|
// We want the realm emoji to overwrite any existing entry in this map.
|
|
|
|
map.set(realm_emoji_name, emoji_dict);
|
|
|
|
}
|
|
|
|
|
2022-03-25 16:11:27 +01:00
|
|
|
return map;
|
2020-07-25 00:12:17 +02:00
|
|
|
}
|
2020-07-25 02:24:01 +02:00
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
export function update_emojis(realm_emojis) {
|
2020-07-24 00:39:22 +02:00
|
|
|
// The settings code still works with the
|
|
|
|
// server format of the data.
|
2020-07-25 01:02:07 +02:00
|
|
|
server_realm_emoji_data = realm_emojis;
|
2020-07-24 00:39:22 +02:00
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
// all_realm_emojis is emptied before adding the realm-specific emoji
|
2018-03-11 18:55:20 +01:00
|
|
|
// to it. This makes sure that in case of deletion, the deleted realm_emojis
|
2020-07-25 00:12:17 +02:00
|
|
|
// don't persist in active_realm_emojis.
|
|
|
|
all_realm_emojis.clear();
|
|
|
|
active_realm_emojis.clear();
|
2017-06-20 22:50:55 +02:00
|
|
|
|
2020-02-06 02:10:03 +01:00
|
|
|
for (const data of Object.values(realm_emojis)) {
|
2020-07-25 00:12:17 +02:00
|
|
|
all_realm_emojis.set(data.id, {
|
2020-02-06 00:08:06 +01:00
|
|
|
id: data.id,
|
|
|
|
emoji_name: data.name,
|
|
|
|
emoji_url: data.source_url,
|
2021-08-12 10:20:50 +02:00
|
|
|
still_url: data.still_url,
|
2020-02-06 00:08:06 +01:00
|
|
|
deactivated: data.deactivated,
|
|
|
|
});
|
2017-06-20 22:50:55 +02:00
|
|
|
if (data.deactivated !== true) {
|
2020-07-25 00:12:17 +02:00
|
|
|
active_realm_emojis.set(data.name, {
|
2020-02-06 00:17:30 +01:00
|
|
|
id: data.id,
|
|
|
|
emoji_name: data.name,
|
|
|
|
emoji_url: data.source_url,
|
2021-08-12 10:20:50 +02:00
|
|
|
still_url: data.still_url,
|
2020-02-06 00:17:30 +01:00
|
|
|
});
|
2017-06-20 22:50:55 +02:00
|
|
|
}
|
2020-02-06 02:10:03 +01:00
|
|
|
}
|
2021-11-19 13:49:00 +01:00
|
|
|
|
|
|
|
// Add the special Zulip emoji as though it were a realm emoji.
|
|
|
|
|
|
|
|
// The Zulip emoji is the only emoji that uses a string ("zulip")
|
|
|
|
// as its ID. All other emoji use numeric IDs. This special case
|
|
|
|
// is confusing; ideally we'd convert the Zulip emoji to be
|
|
|
|
// implemented using the RealmEmoji infrastructure.
|
2020-07-25 00:12:17 +02:00
|
|
|
all_realm_emojis.set("zulip", zulip_emoji);
|
2021-11-19 13:49:00 +01:00
|
|
|
|
|
|
|
// here "zulip" is an emoji name, which is fine.
|
2020-07-25 00:12:17 +02:00
|
|
|
active_realm_emojis.set("zulip", zulip_emoji);
|
2017-05-01 01:13:28 +02:00
|
|
|
|
2022-03-25 16:11:27 +01:00
|
|
|
emojis_by_name = build_emojis_by_name({
|
|
|
|
realm_emojis: active_realm_emojis,
|
|
|
|
emoji_catalog: emoji_codes.emoji_catalog,
|
|
|
|
get_emoji_name,
|
|
|
|
default_emoji_aliases,
|
|
|
|
});
|
2020-07-25 00:12:17 +02:00
|
|
|
}
|
2013-08-22 19:54:35 +02:00
|
|
|
|
2021-07-26 12:43:55 +02:00
|
|
|
// This function will provide required parameters that would
|
|
|
|
// need by template to render an emoji.
|
|
|
|
export function get_emoji_details_by_name(emoji_name) {
|
|
|
|
// To call this function you must pass an emoji name.
|
|
|
|
if (!emoji_name) {
|
|
|
|
throw new Error("Emoji name must be passed.");
|
|
|
|
}
|
|
|
|
|
|
|
|
if (active_realm_emojis.has(emoji_name)) {
|
|
|
|
const emoji_code_info = active_realm_emojis.get(emoji_name);
|
2023-04-05 12:51:26 +02:00
|
|
|
return {
|
|
|
|
emoji_name,
|
|
|
|
emoji_code: emoji_code_info.id,
|
|
|
|
url: emoji_code_info.emoji_url,
|
|
|
|
still_url: emoji_code_info.still_url,
|
|
|
|
reaction_type: emoji_name === "zulip" ? "zulip_extra_emoji" : "realm_emoji",
|
|
|
|
};
|
|
|
|
}
|
|
|
|
|
|
|
|
const codepoint = get_emoji_codepoint(emoji_name);
|
|
|
|
if (codepoint === undefined) {
|
|
|
|
throw new Error("Bad emoji name: " + emoji_name);
|
2021-07-26 12:43:55 +02:00
|
|
|
}
|
2023-04-05 12:51:26 +02:00
|
|
|
|
|
|
|
return {
|
|
|
|
emoji_name,
|
|
|
|
reaction_type: "unicode_emoji",
|
|
|
|
emoji_code: codepoint,
|
|
|
|
};
|
2021-07-26 12:43:55 +02:00
|
|
|
}
|
|
|
|
|
user_status: Fix status emoji handling of deactivated custom emoji.
Previously, if a user had a realm emoji set as their status emoji and
someone deleted the realm emoji, the app would fail to initialize,
because of the error we throw from `./shared/js/emoji.js`.
This commit fixes this by just displaying the deactivated emoji,
similar to how we do when realm_emoji used as reactions are deleted.
As part of the fix, we add a function get_emoji_details_for_rendering,
which duplicates some of the logic used in `reactions.js`, we can
refactor to remove the duplication in `reactions.js` in future
commits.
Note that the following behaviour is a part of our design:
If a user sets their emoji to a particular realm emoji, say for
example "octo-ninja", and "octo-ninja" was then deleted, and a new
emoji was added with the name "octo-ninja", the user's status emoji
would change to show the new emoji instead of the deleted emoji.
Also note that in the `user_status.js` node test, we were able to
change the name for the 991 realm_emoji because it had not been
previously used anywhere in the test (possibly added as just a copy
paste artifact?).
Fixes: #20274.
emoji: Use reaction_type parameter to analyze emoji.
2021-11-20 10:14:52 +01:00
|
|
|
export function get_emoji_details_for_rendering(opts) {
|
|
|
|
if (!opts.emoji_name || !opts.emoji_code || !opts.reaction_type) {
|
|
|
|
throw new Error("Invalid params.");
|
|
|
|
}
|
|
|
|
|
|
|
|
if (opts.reaction_type !== "unicode_emoji") {
|
|
|
|
const realm_emoji = all_realm_emojis.get(opts.emoji_code);
|
|
|
|
if (!realm_emoji) {
|
|
|
|
throw new Error(`Cannot find realm emoji for code '${opts.emoji_code}'.`);
|
|
|
|
}
|
|
|
|
return {
|
|
|
|
url: realm_emoji.emoji_url,
|
|
|
|
still_url: realm_emoji.still_url,
|
|
|
|
emoji_name: opts.emoji_name,
|
|
|
|
emoji_code: opts.emoji_code,
|
|
|
|
reaction_type: opts.reaction_type,
|
|
|
|
};
|
|
|
|
}
|
|
|
|
// else
|
|
|
|
return {
|
|
|
|
emoji_name: opts.emoji_name,
|
|
|
|
emoji_code: opts.emoji_code,
|
|
|
|
reaction_type: opts.reaction_type,
|
|
|
|
};
|
|
|
|
}
|
|
|
|
|
2022-03-25 17:52:12 +01:00
|
|
|
function build_default_emoji_aliases({names, get_emoji_codepoint}) {
|
|
|
|
// Please keep this as a pure function so that we can
|
|
|
|
// eventually share this code with the mobile codebase.
|
|
|
|
|
|
|
|
// Create a map of codepoint -> names
|
|
|
|
const map = new Map();
|
|
|
|
|
|
|
|
for (const name of names) {
|
|
|
|
const base_name = get_emoji_codepoint(name);
|
|
|
|
|
|
|
|
if (map.has(base_name)) {
|
|
|
|
map.get(base_name).push(name);
|
|
|
|
} else {
|
|
|
|
map.set(base_name, [name]);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return map;
|
|
|
|
}
|
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
export function initialize(params) {
|
2020-07-25 23:59:49 +02:00
|
|
|
emoji_codes = params.emoji_codes;
|
|
|
|
|
2022-03-25 15:22:37 +01:00
|
|
|
emoticon_translations = build_emoticon_translations({
|
|
|
|
emoticon_conversions: emoji_codes.emoticon_conversions,
|
|
|
|
});
|
2020-07-25 23:59:49 +02:00
|
|
|
|
2022-03-25 17:52:12 +01:00
|
|
|
default_emoji_aliases = build_default_emoji_aliases({
|
|
|
|
names: emoji_codes.names,
|
|
|
|
get_emoji_codepoint,
|
|
|
|
});
|
2017-08-16 22:00:19 +02:00
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
update_emojis(params.realm_emoji);
|
|
|
|
}
|
2015-10-15 22:34:30 +02:00
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
export function get_canonical_name(emoji_name) {
|
|
|
|
if (active_realm_emojis.has(emoji_name)) {
|
2017-09-29 22:14:57 +02:00
|
|
|
return emoji_name;
|
|
|
|
}
|
2020-07-25 00:12:17 +02:00
|
|
|
const codepoint = get_emoji_codepoint(emoji_name);
|
2020-05-27 04:17:29 +02:00
|
|
|
if (codepoint === undefined) {
|
2020-07-24 23:30:57 +02:00
|
|
|
// Our caller needs to handle this possibility.
|
2020-09-24 07:50:36 +02:00
|
|
|
return undefined;
|
2017-09-29 22:14:57 +02:00
|
|
|
}
|
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
return get_emoji_name(codepoint);
|
|
|
|
}
|
2018-01-15 19:36:32 +01:00
|
|
|
|
2020-07-25 00:12:17 +02:00
|
|
|
export function get_emoticon_translations() {
|
|
|
|
return emoticon_translations;
|
|
|
|
}
|