# `ClothingSize`

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

Use it for clothes in a shop. For shoes, use [`ShoeSize`](/docs/types/type-shoe-size.md).

## Shape

| Field | Type | Required? |
|---|---|---|
| `system` | [`ClothingSizeSystem`](/docs/types/type-clothing-size-system.md) | Yes |
| `size` | `Text` | Yes |

## Example

```jadpo
ClothingSize { system: ClothingSizeSystem.uk size: "10" }
```

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

## Good to know

- Two sizes in different systems aren't compared or converted. `UK 10` and `EU 38` are simply different values.
- `==` tells you whether two are the same. `<` and `list.sort_by` don't take it, so sort by one of its parts instead.

## In JSON

A string, in a request, a response or `json.write`:

```json
"UK 10"
"EU 38"
"US 00"
```

## Details

<details>
<summary>Text form, storage, how it is shown, and operations</summary>

`ClothingSize` is in the group Commerce and logistics, and has been in Jadpo since 0.1.0.

### Text form

`text.from` writes one standard text form, the same form `text.parse` reads back: `UK 10`, `EU 38` and `US 00`.

### How it is stored

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'` |

### How it is 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 also takes `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. [How every standard type behaves](/docs/every-standard-type-meets-one-contract.md) says how they work.

</details>