Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 1 Nov 2026. What's built · Install 0.2.0
jadpo
Reference: Standard library

Standard types

WebOrigin

On this page

A web origin (RFC 6454): http or https, the host, and a port only where it isn't the scheme's default: https://example.com, http://localhost:8080.

Web and network; not ordered; since Jadpo 0.1.0.

Make one

Build one from its text, WebOrigin("https://example.com"), which checks it: text that isn't one breaks format.

text.parse(raw, as: WebOrigin) reads one from its text; text that isn't one at all fails malformed, such as https://example.com/, https://example.com:443 or http://example.com:80.

Text, JSON and storage

text.from writes its canonical text, the one form text.parse reads back. JSON sends its canonical text as a string.

Text JSON
https://example.com "https://example.com"
http://localhost:8080 "http://localhost:8080"
https://[2001:db8::1] "https://[2001:db8::1]"
http://192.0.2.1:3000 "http://192.0.2.1:3000"

It is stored in one column named for the field, of type text. https://[2001:db8::1] is stored as 'https://[2001:db8::1]'.

Shown to people

text.format(value, locale:) shows it to people in their locale.

With locale: Locale.en_gb:

Value Shown
https://example.com https://example.com
http://localhost:8080 http://localhost:8080
https://[2001:db8::1] https://[2001:db8::1]
http://192.0.2.1:3000 http://192.0.2.1:3000

Operations

It has the contract's own operations: text.parse, text.from, text.format, json.read, json.write and ==. It isn't ordered, so < and sorting don't take it. Every standard type meets one contract says how they work.

Markdown for agents: /docs/types/type-web-origin.md.Built from Jadpo main at e00e61f.