# `HttpMethod`

An HTTP method (RFC 9110), one a route is written with, written as its token, `GET`.

[Web and network](types.md#web-and-network); not ordered; since Jadpo 0.1.0.

## Make one

Pick one of its variants, `HttpMethod.get`.

`text.parse(raw, as: HttpMethod)` reads one from its text; text that isn't one at all fails `malformed`, such as `FETCH`, `HEAD` or `GET `.

## Variants

| Variant | Written |
|---|---|
| `get` | `GET` |
| `post` | `POST` |
| `put` | `PUT` |
| `patch` | `PATCH` |
| `delete` | `DELETE` |

## 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 |
|---|---|
| `GET` | `"GET"` |
| `PATCH` | `"PATCH"` |
| `DELETE` | `"DELETE"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `GET` | `GET` |
| `PATCH` | `PATCH` |
| `DELETE` | `DELETE` |

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