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

Vin

On this page

A vehicle identification number (ISO 3779), 17 characters with no I, O or Q: 1HGCM82633A004352.

Commerce and logistics; not ordered; since Jadpo 0.1.0.

Make one

Build one from its text, Vin("1HGCM82633A004352"), which checks it: text that isn't one breaks format.

text.parse(raw, as: Vin) reads one from its text; text that isn't one at all fails malformed, such as 1M8GDM9AYKP042788, 1M8GDM9AXKP04278O or 1m8gdm9axkp042788.

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
1HGCM82633A004352 "1HGCM82633A004352"
1M8GDM9AXKP042788 "1M8GDM9AXKP042788"
WVWZZZ1JZXW000001 "WVWZZZ1JZXW000001"

It is stored in one column named for the field, of type text. 1M8GDM9AXKP042788 is stored as '1M8GDM9AXKP042788'.

Shown to people

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

With locale: Locale.en_gb:

Value Shown
1HGCM82633A004352 1HGCM82633A004352
1M8GDM9AXKP042788 1M8GDM9AXKP042788
WVWZZZ1JZXW000001 WVWZZZ1JZXW000001

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-vin.md.Built from Jadpo main at e00e61f.