Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 30 Oct 2026. What's built · Install 0.1.0
jadpo
Reference: HTTP

HTTP · rule

route.header_not_scalar

Header field is not a single value.

Area 7, HTTP; not declinable; the next step is usually the agent's.

A header holds one value:

example
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    }}type TaggedMemo = Input {    text: Memo    tags: List<Memo> {        header: "X-Tags"        optional: true    }}action add_tagged_memo(input: TaggedMemo) -> MemoView {    return MemoView {        text: input.text    }}policy {    actions: {        add_tagged_memo: [Access.public]    }}routes Memos {    prefix: /memos    POST / {        authentication: RouteAuthentication.none        input: TaggedMemo        output: MemoView        run: add_tagged_memo(input)    }}
text
error: A header can't hold `List<Memo>` --> main.jadpo:24:17   |24 |         header: "X-Tags"   |                 ^^^^^^^^ one value per header  reason: A header holds one value, so a field read from one is a scalar or an enum without data; lists and objects come in the body.  next: Move the field to the body, or give it a scalar type (agent)  rule: route.header_not_scalar  help: https://jadpo.dev/docs/errors/route.header_not_scalarcheck failed: 1 error, 1 file

Markdown for agents: /docs/errors/route.header_not_scalar.md.Built from Jadpo main at a707efb.