# `Year`

A calendar year: `2026`.

Use it for a tax year's label or a year of publication, from 0 to 9999. In JSON it is a string. For a plain count of years, use [`CalendarPeriod`](/docs/types/type-calendar-period.md).

## Shape

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

## Example

```jadpo
Year { year: 2026 }
```

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

## 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
"1999"
"2026"
```

## Details

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

`Year` 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: `1999` and `2026`.

### How it is stored

It is stored in one column named for the field, of type `smallint`. `2026` is stored as `2026`.

### How it is shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `1999` | `1999` |
| `2026` | `2026` |

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