Skip to content
OriginChats

emoji_update

emoji_update is implemented by handleEmojiUpdate in src/api/handlers/emoji/emoji_update.osl.

Handles the emoji update protocol operation through the resource-specific helper and storage layers.

Access

Section titled “Access”
Gate Requirement
Authentication Required by the central API gate.
Central permission manage_emojis
Broadcast Not marked global directly by this adapter. A helper may emit focused or server-wide updates.

Request

Section titled “Request”

Every request includes cmd: "emoji_update" and may include an opaque listener correlation value.

Field Validation / meaning
name schema.string()
image schema.string()
emoji_id Read separately by the handler or a shared domain helper

Validator source

Section titled “Validator source”

The handler and shared validation path use these OSL schema definitions before normalization:

*schema.Schema schemaEmojiUpdate = schema.object({
  name: schema.string(),
  image: schema.string()
}).partial().requireAnyValue(["name", "image"])

Processing path

Section titled “Processing path”
  1. handleCmd enforces authentication and the manage_emojis permission.
  2. dispatchCmd routes emoji_update to handleEmojiUpdate.
  3. The adapter validates and normalizes input, then calls its domain collaborators.
  4. Durable mutations complete before the response or event is returned.
  5. onMessage adds the request listener to direct responses and performs any marked broadcast.

Direct collaborators visible in the handler: customAssetId, emojiUpdate, true, customAssetFields

Responses and events

Section titled “Responses and events”

Response/event command names visible in this adapter: emoji_update.

Validation and domain failures use:

{
  "cmd": "error",
  "val": "<message>",
  "src": "emoji_update",
  "listener": "<copied from request>"
}