# `CallingCode`

A country calling code (ITU-T E.164) with its `+`: `+44`.

[Places](types.md#places); not ordered; since Jadpo 0.1.0.

## Make one

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

`text.parse(raw, as: CallingCode)` reads one from its text; text that isn't one at all fails `malformed`, such as `44`, `+0` or `+999`.

## 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 |
|---|---|
| `+1` | `"+1"` |
| `+44` | `"+44"` |
| `+800` | `"+800"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `+1` | `+1` |
| `+44` | `+44` |
| `+800` | `+800` |

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