needs.yaml may name the tones
Test / test (push) Successful in 1m16s

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt
This commit is contained in:
Bendik Aagaard Lynghaug
2026-09-30 15:17:20 +02:00
co-authored by Claude Fable 5.1
parent 050fb34fb0
commit e3c68f9441
2 changed files with 9 additions and 0 deletions
+4
View File
@@ -3,6 +3,10 @@
One line per change, grouped by the release that shipped it. Newest One line per change, grouped by the release that shipped it. Newest
first. Each release names the portal tag it is built against. first. Each release names the portal tag it is built against.
## Unreleased
- `needs.yaml` may name the site's `tones`, one storyline each; the checks read the first storyline, which is what `build_questions` gives.
## 0.5.10 (2026-09-30) - portal v0.5.10 ## 0.5.10 (2026-09-30) - portal v0.5.10
- Matches portal v0.5.10 (released by portal's publish job). - Matches portal v0.5.10 (released by portal's publish job).
+5
View File
@@ -36,6 +36,11 @@ pub struct NeedsFile {
pub needs: Vec<Need>, pub needs: Vec<Need>,
#[serde(default)] #[serde(default)]
pub personas: Vec<Persona>, pub personas: Vec<Persona>,
/// The tones of voice the site is told in, one storyline each
/// (portal docs, Storylines). Named here so the report can say
/// which tone a storyline index is; the checks read the first.
#[serde(default)]
pub tones: Vec<String>,
} }
#[derive(Debug, Deserialize)] #[derive(Debug, Deserialize)]