You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to offer the user a UI to choose an emoji from the emoji Zulip knows about, we'll need to know what emoji those are and what Zulip calls them.
Zulip has a particular data model for identifying emoji, which is an underdocumented part of the Zulip API. For an introduction, see reaction_type here: https://zulip.com/api/add-reaction#parameter-reaction_type
and the two companion fields emoji_code and emoji_name. (The same emoji model is used for reactions as for emoji in messages.)
Then see zulip-mobile's src/emoji/data.js, which tracks this model.
A good implementation of this issue will:
Cover all three of Zulip's types of emoji.
Support efficiently looking up an emoji by name, or by type and code.
Support iterating through the list of all Zulip emoji.
The text was updated successfully, but these errors were encountered:
gnprice
added
a-api
Implementing specific parts of the Zulip server API
a-model
Implementing our data model (PerAccountStore, etc.)
labels
May 13, 2024
This is a prerequisite for:
In order to offer the user a UI to choose an emoji from the emoji Zulip knows about, we'll need to know what emoji those are and what Zulip calls them.
Zulip has a particular data model for identifying emoji, which is an underdocumented part of the Zulip API. For an introduction, see
reaction_type
here:https://zulip.com/api/add-reaction#parameter-reaction_type
and the two companion fields
emoji_code
andemoji_name
. (The same emoji model is used for reactions as for emoji in messages.)Then see zulip-mobile's
src/emoji/data.js
, which tracks this model.A good implementation of this issue will:
The text was updated successfully, but these errors were encountered: