Skip to content
OriginChats

emoji_delete

emoji_delete is implemented by handleEmojiDelete in src/api/handlers/emoji/emoji_delete.osl.

Handles the emoji delete 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_delete" and may include an opaque listener correlation value.

Field Validation / meaning
emoji_id Read separately by the handler or a shared domain helper

Validator source

Section titled “Validator source”

This adapter delegates validation to a shared helper. The field table lists values read directly by the handler; follow the collaborators below for the shared domain schema.

Processing path

Section titled “Processing path”
  1. handleCmd enforces authentication and the manage_emojis permission.
  2. dispatchCmd routes emoji_delete to handleEmojiDelete.
  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, emojiDelete

Responses and events

Section titled “Responses and events”

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

Validation and domain failures use:

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