list-unsubscribe 0.1.0

Parse RFC 2369 List-Unsubscribe and RFC 8058 List-Unsubscribe-Post headers into a typed action enum.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

# Conformance corpus

JSON test fixtures that pin the public contract of `list-unsubscribe`.

The format is deliberately language-neutral so a future TypeScript port,
or any other implementation, can adopt the corpus without reverse-engineering
Rust tests. See [`schema.json`](./schema.json) for the structure.

Each fixture file has the shape:

```json
{
  "name": "rfc2369-mailto-only",
  "description": "Single mailto URI in List-Unsubscribe, no Post header.",
  "spec": {
    "source": "RFC 2369",
    "url": "https://www.rfc-editor.org/rfc/rfc2369#section-3.2",
    "behavior": "..."
  },
  "input": {
    "list_unsubscribe": "<mailto:u@example.com>",
    "list_unsubscribe_post": null
  },
  "expected": {
    "kind": "Mailto",
    "address": "u@example.com",
    "subject": null
  }
}
```

`expected.kind` is one of `OneClick`, `HttpLink`, `Mailto`, or `None`. The
remaining fields depend on the variant — `url` for the HTTP variants,
`address` and `subject` for `Mailto`.

The mapping from each fixture to the behavior it pins lives in
[`coverage.md`](./coverage.md). The test suite enforces three things:

1. Every fixture file is referenced in `coverage.md`.
2. Every contract-critical fixture name in
   [`tests/conformance.rs`](../tests/conformance.rs) has a corresponding
   JSON file.
3. The actual parser output for each fixture matches `expected`.

## Adding a fixture

1. Write the JSON under `conformance/<descriptive-name>.json`.
2. Add a row to `coverage.md`.
3. If the fixture pins a contract-level guarantee (not just an edge
   case), also add its name to the `required` array in
   `tests/conformance.rs`.
4. Run `cargo test -p list-unsubscribe --all-features --tests`.