# `LocalTime`

A clock time with no date or zone, to the second, written `09:30:00`: `hour` from 0 to 23, `minute` and `second` from 0 to 59.

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

## Make one

Build one from its fields, `LocalTime { hour: ...  minute: ...  second: ... }`.

`text.parse(raw, as: LocalTime)` reads one from its text; text that isn't one at all fails `malformed`, such as `24:00:00`, `09:30` or `9:30:00`.

## Fields

| Field | Type |
|---|---|
| `hour` | `Int` |
| `minute` | `Int` |
| `second` | `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:00:00"` |
| `09:30:00` | `"09:30:00"` |
| `23:59:59` | `"23:59:59"` |

It is stored in one column named for the field, of type `time`. `09:30:00` is stored as `'09:30:00.000000'::time`.

## Shown to people

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

With `locale: Locale.en_gb` and `format: TimeFormat.time_medium`:

| Value | Shown |
|---|---|
| `00:00:00` | `00:00:00` |
| `09:30:00` | `09:30:00` |
| `23:59:59` | `23:59:59` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It is ordered, so `<` and sorting take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.