# `Weekday`

A day of the week.

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

## Make one

Pick one of its variants, `Weekday.monday`.

`text.parse(raw, as: Weekday)` reads one from its text; text that isn't one at all fails `malformed`, such as `mon` or `funday`.

This operation gives one: `temporal.weekday`.

## Variants

7 variants, each written as its own name: `monday`, `tuesday`, `wednesday`, `thursday`, `friday`, `saturday`, `sunday`.

## 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 |
|---|---|
| `monday` | `"monday"` |
| `sunday` | `"sunday"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `monday` | `Monday` |
| `sunday` | `Sunday` |

## Operations

- `temporal.week_bounds(date: CalendarDate, zone: Zone, starts_on: Weekday) -> InstantRange`: The week holding `date` in `zone`, starting on `starts_on`.
- `temporal.weekday(value: T) -> Weekday`: The day of the week.

Like every standard type, it also 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.