# `Quarter`

A quarter of a calendar year: `2026-Q4`.

Use it for financial reports by quarter. Quarters here follow the calendar year, so for a financial year with another start, keep your own type.

## Shape

| Field | Type | Required? |
|---|---|---|
| `year` | `Int` | Yes |
| `quarter` | `Int` | Yes |

## Example

```jadpo
Quarter { year: 2026 quarter: 4 }
```

`text.parse(raw, as: Quarter)` reads one from text that comes from outside. Text that isn't one at all fails `malformed`, such as `2026-Q5`, `2026-Q0` or `2026Q1`.

## Good to know

- `==` tells you whether two are the same, and `<` and `list.sort_by` compare and sort them.

## In JSON

A string, in a request, a response or `json.write`:

```json
"2026-Q1"
"2026-Q4"
```

## Details

<details>
<summary>Text form, storage, how it is shown, and operations</summary>

`Quarter` is in the group Time and calendar, and has been in Jadpo since 0.1.0.

### Text form

`text.from` writes one standard text form, the same form `text.parse` reads back: `2026-Q1` and `2026-Q4`.

### How it is stored

It is stored in 2 columns, each named for the field, `_` and its suffix. This is `2026-Q4`:

| Column | Type | Holds |
|---|---|---|
| `<field>_year` | `smallint` | `2026` |
| `<field>_quarter` | `smallint` | `4` |

### How it is shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `2026-Q1` | `2026-Q1` |
| `2026-Q4` | `2026-Q4` |

### Operations

It also takes `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. [How every standard type behaves](/docs/every-standard-type-meets-one-contract.md) says how they work.

</details>