# `UtcOffset`

An offset from UTC in minutes, written `+05:30`, from 18 hours behind to 18 hours ahead.

[Time and calendar](types.md#time-and-calendar); not ordered; since Jadpo 0.1.0.

## Make one

Build one from its fields, `UtcOffset { minutes: ... }`.

`text.parse(raw, as: UtcOffset)` reads one from its text; text that isn't one at all fails `malformed`, such as `Z`, `+0100` or `+01`.

## Fields

| Field | Type |
|---|---|
| `minutes` | `Int` |

## 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 |
|---|---|
| `+00:00` | `"+00:00"` |
| `+05:30` | `"+05:30"` |
| `-05:00` | `"-05:00"` |

It is stored in one column named for the field, of type `smallint`. `+05:30` is stored as `330`.

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `+00:00` | `GMT+00:00` |
| `+05:30` | `GMT+05:30` |
| `-05:00` | `GMT-05:00` |

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