sticker_delete
sticker_delete is implemented by handleStickerDelete in src/api/handlers/sticker/sticker_delete.osl.
Handles the sticker 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: "sticker_delete" and may include an opaque listener correlation value.
| Field | Validation / meaning |
|---|---|
sticker_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”handleCmdenforces authentication and themanage_emojispermission.dispatchCmdroutessticker_deletetohandleStickerDelete.- 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: customAssetId, stickerDelete
Responses and events
Section titled “Responses and events”Response/event command names visible in this adapter: sticker_delete.
Validation and domain failures use:
{ "cmd": "error", "val": "<message>", "src": "sticker_delete", "listener": "<copied from request>"}