# `Imei`

A mobile device's IMEI (3GPP TS 23.003): 15 digits, its Luhn check digit passing. Personal data.

[Web and network](types.md#web-and-network); not ordered; personal data (online); since Jadpo 0.1.0.

## Make one

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

`text.parse(raw, as: Imei)` reads one from its text; text that isn't one at all fails `malformed`, such as `490154203237519`, `49015420323751` or `4901542032375180`.

## 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 |
|---|---|
| `490154203237518` | `"490154203237518"` |
| `356938035643809` | `"356938035643809"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `490154203237518` | `490154203237518` |
| `356938035643809` | `356938035643809` |

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