# `LawfulBasis`

A lawful basis for processing personal data (GDPR Article 6(1)), written as its own name, `legitimate_interests`.

[Other with a published standard](types.md#other-with-a-published-standard); not ordered; since Jadpo 0.1.0.

## Make one

Pick one of its variants, `LawfulBasis.consent`.

`text.parse(raw, as: LawfulBasis)` reads one from its text; text that isn't one at all fails `malformed`, such as `legitimate interests`, `6(1)(f)` or `f`.

## Variants

6 variants, each written as its own name: `consent`, `contract`, `legal_obligation`, `legitimate_interests`, `public_task`, `vital_interests`.

## 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 |
|---|---|
| `consent` | `"consent"` |
| `legitimate_interests` | `"legitimate_interests"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `consent` | `Consent` |
| `legitimate_interests` | `Legitimate interests` |

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