sticker_add
sticker_add is implemented by handleStickerAdd in src/api/handlers/sticker/sticker_add.osl.
Handles the sticker add 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: "sticker_add" and may include an opaque listener correlation value.
| Field | Validation / meaning |
|---|---|
name |
schema.string() |
image |
schema.string() |
description |
schema.string().defaultValue("") |
Validator source
Section titled “Validator source”The handler and shared validation path use these OSL schema definitions before normalization:
*schema.Schema schemaStickerAdd = schema.object({ name: schema.string(), image: schema.string(), description: schema.string().defaultValue("")})Processing path
Section titled “Processing path”handleCmdenforces authentication and themanage_emojispermission.dispatchCmdroutessticker_addtohandleStickerAdd.- The adapter validates and normalizes input, then calls its domain collaborators.
- Durable mutations complete before the response or event is returned.
onMessageadds the request listener to direct responses and performs any marked broadcast.
Direct collaborators visible in the handler: stickerAdd, customAssetFields
Responses and events
Section titled “Responses and events”Response/event command names visible in this adapter: sticker_add.
Validation and domain failures use:
{ "cmd": "error", "val": "<message>", "src": "sticker_add", "listener": "<copied from request>"}