# `MacAddress`

A hardware address (IEEE 802's EUI-48) in IEEE's form, six pairs of upper-case hexadecimal digits joined by `-`: `AC-DE-48-00-00-80`. 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, `MacAddress("AC-DE-48-00-00-80")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: MacAddress)` reads one from its text; text that isn't one at all fails `malformed`, such as `ac-de-48-00-00-80`, `AC:DE:48:00:00:80` or `ACDE48000080`.

## 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 |
|---|---|
| `AC-DE-48-00-00-80` | `"AC-DE-48-00-00-80"` |
| `00-00-5E-00-53-01` | `"00-00-5E-00-53-01"` |

It is stored in one column named for the field, of type `text`. `00-00-5E-00-53-01` is stored as `'00-00-5E-00-53-01'`.

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `AC-DE-48-00-00-80` | `AC-DE-48-00-00-80` |
| `00-00-5E-00-53-01` | `00-00-5E-00-53-01` |

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