# `ClothingSizeSystem`

Which system a clothing size is in: `UK`, `EU` or `US`.

Use it as part of a [`ClothingSize`](/docs/types/type-clothing-size.md), or to remember which sizes a shopper prefers.

## Shape

One of these 3 values:

| Value | Written |
|---|---|
| `ClothingSizeSystem.uk` | `UK` |
| `ClothingSizeSystem.eu` | `EU` |
| `ClothingSizeSystem.us` | `US` |

## Example

```jadpo
ClothingSizeSystem.uk
```

`text.parse(raw, as: ClothingSizeSystem)` reads one from text that comes from outside. Text that isn't one at all fails `malformed`, such as `FR`, `Europe` or `UK `.

## Good to know

- `==` tells you whether two are the same. `<` and `list.sort_by` don't take it.

## In JSON

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

```json
"UK"
"EU"
"US"
```

## Details

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

`ClothingSizeSystem` 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`, `EU` and `US`.

### How it is stored

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

### 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` | `UK` |
| `EU` | `EU` |
| `US` | `US` |

### 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>