Url
An http:// or https:// URL with a host.
Web and network; not ordered; since Jadpo 0.1.0.
Make one
text.parse(raw, as: Url) reads one from its text; text that isn't one at all fails malformed, such as example.com or ftp://example.com.
These operations give one: web.resolve and web.with_query.
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/orders |
"https://example.com/orders" |
It is stored in one column named for the field, of type text. https://example.com/orders is stored as 'https://example.com/orders'.
Shown to people
text.format(value, locale:) shows it to people in their locale.
With locale: Locale.en_gb:
| Value | Shown |
|---|---|
https://example.com/orders |
https://example.com/orders |
Operations
web.resolve(base: Url, relative: RelativeUrl) -> Url:relativeresolved againstbaseby RFC 3986 (section 5.2): its.and..segments followed, a path starting/taken from the host, a query or a fragment alone kept with the base's path. AUrlPathis aRelativeUrl, so it resolves too.web.with_query(url: Url, entries: Map<Text, Text>) -> Url:urlwith each ofentriesadded to its query askey=value, in key order, each percent-encoded asencoding.to_url_componentencodes it, after any queryurlhas and before its fragment.
Like every standard type, it also 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-url.md.Built from Jadpo main at e00e61f.