HTTP · rule
route.output_unexpected
A no_content route has an output.
Area 7, HTTP; not declinable; the next step is usually the agent's.
A no_content route sends no body:
type Memo = Text { max_length: 200}type MemoId = Uuid {}type AddMemo = Input { text: Memo}type MemoView = Output { text: Memo}action add_memo(input: AddMemo) -> MemoView { return MemoView { text: input.text }}routes Memos { prefix: /memos POST / { input: AddMemo output: MemoView status: SuccessStatus.no_content run: add_memo(input) }}
error: `POST /memos` answers with no content --> main.jadpo:26:9 |26 | output: MemoView | ^^^^^^^^^^^^^^^^ no body is sent reason: `SuccessStatus.no_content` answers 204 with no body, so the route has no `output:` and what it runs returns `Unit`. next: Remove `output:`, or choose another status (agent) rule: route.output_unexpected help: https://jadpo.dev/docs/errors/route.output_unexpectedcheck failed: 1 error, 1 file
Markdown for agents: /docs/errors/route.output_unexpected.md.Built from Jadpo main at a707efb.