# `IataAirline`

An airline's IATA designator, two characters: `BA`.

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

## Make one

Build one from its text, `IataAirline("BA")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: IataAirline)` reads one from its text; text that isn't one at all fails `malformed`, such as `ba`, `99` or `B`.

## 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 |
|---|---|
| `BA` | `"BA"` |
| `U2` | `"U2"` |
| `6E` | `"6E"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `BA` | `BA` |
| `U2` | `U2` |
| `6E` | `6E` |

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