# `CabinClass`

The cabin a seat is sold in, written as its own name, `premium_economy`.

[Travel](types.md#travel); not ordered; since Jadpo 0.1.0.

## Make one

Pick one of its variants, `CabinClass.business`.

`text.parse(raw, as: CabinClass)` reads one from its text; text that isn't one at all fails `malformed`, such as `coach`, `premium economy` or `J`.

## Variants

4 variants, each written as its own name: `business`, `economy`, `first`, `premium_economy`.

## 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 |
|---|---|
| `economy` | `"economy"` |
| `premium_economy` | `"premium_economy"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `economy` | `Economy` |
| `premium_economy` | `Premium economy` |

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