Skip to content
OriginChats

thread_leave

thread_leave is implemented by handleThreadLeave in src/api/handlers/thread/thread_leave.osl.

Handles the thread leave 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 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: "thread_leave" and may include an opaque listener correlation value.

Field Validation / meaning
thread_id schema.string().minLen(1)

Validator source

Section titled “Validator source”

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

*schema.Schema schemaThreadLeave = schema.object({
  thread_id: schema.string().minLen(1)
})

Processing path

Section titled “Processing path”
  1. handleCmd enforces authentication.
  2. dispatchCmd routes thread_leave to handleThreadLeave.
  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: threadFromId, threadRemoveParticipant, threadPublicWithLast, usernameFromId

Responses and events

Section titled “Responses and events”

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

Validation and domain failures use:

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