Skip to content
OriginChats

typing

typing is implemented by handleTyping in src/api/handlers/typing.osl.

duration defaults to 6000 and is forwarded unchanged as a client display hint. The server does not convert or enforce a unit.

Access

Section titled “Access”
Gate Requirement
Authentication Required by the central API gate.
Central permission None. Resource, channel, ownership, or hierarchy checks may still apply in the handler/helpers.
Broadcast Yes. The transport removes the internal marker and filters recipients by channel visibility.

Request

Section titled “Request”

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

Field Validation / meaning
channel schema.string().defaultValue("")
thread_id schema.string().defaultValue("")
duration schema.integer().min(0).defaultValue(6000)
sent_at schema.number().optional()

Validator source

Section titled “Validator source”

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

*schema.Schema schemaTyping = schema.object({
  channel: schema.string().defaultValue(""),
  thread_id: schema.string().defaultValue(""),
  duration: schema.integer().min(0).defaultValue(6000),
  sent_at: schema.number().optional()
})

Processing path

Section titled “Processing path”
  1. handleCmd enforces authentication.
  2. dispatchCmd routes typing to handleTyping.
  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: messageContext, usernameFromId, typeof

Responses and events

Section titled “Responses and events”

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

Validation and domain failures use:

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