# `LogLevel`

How severe a log record is: `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR` or `FATAL`.

Use it to filter or record logs.

## Shape

One of these 6 values:

| Value | Written |
|---|---|
| `LogLevel.trace` | `TRACE` |
| `LogLevel.debug` | `DEBUG` |
| `LogLevel.info` | `INFO` |
| `LogLevel.warn` | `WARN` |
| `LogLevel.error` | `ERROR` |
| `LogLevel.fatal` | `FATAL` |

## Example

```jadpo
LogLevel.warn
```

`text.parse(raw, as: LogLevel)` reads one from text that comes from outside. Text that isn't one at all fails `malformed`, such as `WARNING`, `CRITICAL` or `INFO `.

## Good to know

- `WARNING` and `CRITICAL` are refused, so change them first.
- `==` tells you whether two are the same. `<` and `list.sort_by` don't take it.

## In JSON

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

```json
"TRACE"
"INFO"
"FATAL"
```

## Details

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

`LogLevel` is in the group Software, 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: `TRACE`, `INFO` and `FATAL`.

### How it is stored

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

### How it is shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `TRACE` | `TRACE` |
| `INFO` | `INFO` |
| `FATAL` | `FATAL` |

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