# `ClothingSize`

A clothing size in its system, written as a label writes it: `UK 10`, `US M`.

[Commerce and logistics](types.md#commerce-and-logistics); not ordered; since Jadpo 0.1.0.

## Make one

Build one from its fields, `ClothingSize { system: ...  size: ... }`.

`text.parse(raw, as: ClothingSize)` reads one from its text; text that isn't one at all fails `malformed`, such as `UK10`, `UK  10` or `UK m`.

## Fields

| Field | Type |
|---|---|
| `system` | [`ClothingSizeSystem`](type-clothing-size-system.md) |
| `size` | `Text` |

## 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 |
|---|---|
| `UK 10` | `"UK 10"` |
| `EU 38` | `"EU 38"` |
| `US 00` | `"US 00"` |
| `US M` | `"US M"` |
| `UK 3XL` | `"UK 3XL"` |

It is stored in 2 columns, each named for the field, `_` and its suffix. This is `US 00`:

| Column | Type | Holds |
|---|---|---|
| `<field>_system` | `text` | `'US'` |
| `<field>_size` | `text` | `'00'` |

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `UK 10` | `UK 10` |
| `EU 38` | `EU 38` |
| `US 00` | `US 00` |
| `US M` | `US M` |
| `UK 3XL` | `UK 3XL` |

## 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](../topics/every-standard-type-meets-one-contract.md) says how they work.