Skip to content

sticker_update

sticker_update is implemented by handleStickerUpdate in src/api/handlers/sticker/sticker_update.osl.

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

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.

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

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

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

*schema.Schema schemaStickerUpdate = schema.object({
name: schema.string(),
image: schema.string(),
description: schema.string()
}).partial().requireAnyValue(["name", "image", "description"])
  1. handleCmd enforces authentication and the manage_emojis permission.
  2. dispatchCmd routes sticker_update to handleStickerUpdate.
  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, stickerUpdate, true, customAssetFields

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

Validation and domain failures use:

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