9 Commits
Author SHA1 Message Date
rickandCursor 8e02215f01 openspec: add Purpose sections to all five main specs
OpenSpec 1.16 requires ## Purpose; the specs predate that. Purposes are reconstructed from the 2026-04-13 greenfield proposal and the current requirements. Plain validation now passes 5/5; strict still flags two over-long requirements, tracked in PROJECT_HYGIENE.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-08 12:11:15 +01:00
rickandCursor be00125465 openspec: archive add-french-translation, sync hacs-packaging spec
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-07 18:43:34 +01:00
rick d5f32d956e Merge agent/add-french-translation: French translation by aurel (PR #14), v0.4.6 2026-11-07 18:42:52 +01:00
rickandCursor 529894688b openspec(add-french-translation): apply progress (PR #14 commit, 0.4.6)
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-07 18:36:01 +01:00
rickandCursor c77029188f PROJECT_HYGIENE: UI strings need English and French
PR #14 adds fr.json and a key-parity test; record the rule so agents write the French string instead of relaxing the test.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-07 18:36:01 +01:00
rickandCursor 9a81654579 Version 0.4.6: French translation
Ships the French translation contributed by aurel in PR #14 (704f55e).

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-07 18:35:46 +01:00
rickandCursor 2050051f66 openspec(add-french-translation): propose artifacts
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-07 18:35:09 +01:00
aurel 704f55e595 feat(i18n): add complete French translation (fr.json) 2026-11-07 13:23:59 +01:00
rickandCursor 851ec3a495 openspec: archive add-oktoberfest-keg-art
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-07 12:37:25 +01:00
18 changed files with 257 additions and 4 deletions
+3 -2
View File
@@ -192,13 +192,14 @@ When the user corrects your approach, append a one-line rule here before ending
- **`numberOfPoursSinceStartup` resets to 0 on a machine power cycle** (confirmed 2026-06-01: power-cycled the machine at pours=16, reloaded the integration, Pours read 0). It counts since machine startup, NOT since keg insertion. Do not base keg-change detection on the pour counter — a power cycle (outage, unplug, firmware update) would false-trigger it. `kegVolume` (Keg Remaining) was confirmed unchanged across the same power cycle/reload, so a power cycle produces no spurious volume jump — volume-jump signals (b/c) and the manual button are the power-cycle-safe detectors; prefer them.
- **TODO — verification debt, do this when the next keg is fitted: confirm the keg-freshness baseline survives a reauth.** `fix-reauth-flow` (archived 2026-09-06) was verified on-device for the reauth flow itself, but the machine had no keg in the tap, so there was no freshness countdown to preserve and task 6.6 could not be checked. The fix uses `async_update_reload_and_abort`, which reloads the config entry — the exact moment a `RestoreEntity` baseline could be lost. After the next keg change, trigger a reauth (or reload the integration) and confirm Keg Freshness keeps its countdown instead of resetting to unknown. If it resets, that is a real regression in `PerfectDraftKegFreshnessSensor`'s restore path, not in the config flow.
- **Never add a non-numeric key to `keg_catalog.json`.** `_load_keg_catalog` in `sensor.py` builds `{int(k): v for k, v in raw.items()}` and catches `ValueError` by returning `{}`. A single `_meta` or `_source` key therefore disables the *entire* catalog — every keg reports no name — and says so only at debug level. Recording provenance or attribution inside that file requires changing the loader first. `tests/test_keg_catalog.py::test_keys_are_numeric` guards this.
- **Every UI string change needs English and French (since 0.4.6, 2026-11-07).** When you add, rename or remove a key in `strings.json`, make the same change to `translations/en.json` and `translations/fr.json` in the same commit, keeping each `{placeholder}` name. Write a real French string: no English placeholder, and do not relax `tests/test_translations.py`, which fails on any key mismatch. The maintainer chose strict parity over Home Assistant's English fallback so French never silently falls behind. Keep button and entity names short; they display in narrow UI space.
- **A new integration catalog ID is not done until the card maps it.** The companion card joins on `kegId` against `scripts/keg-catalog.reference.json`. Adding a row to `keg_catalog.json` without binding the card entry (and re-syncing that snapshot) ships a named **Keg** sensor that the card still treats as unknown. The card may already have the beer under a slug with no `kegId` — check before adding a duplicate entry.
- **TODO — verification debt from `backport-keg-catalog` (archived 2026-09-06), clear this after installing v0.3.2 via HACS: confirm the `Keg` sensor still resolves the fitted keg.** The catalog file was replaced wholesale (86 → 114 entries) and verified statically only: exact diff shape, 114 int keys through the loader, and format guards in `tests/test_keg_catalog.py`. What was never exercised is the live path. On-device checks were impossible at the time — no HA on the dev host, and `.credentials.json`'s refresh token had expired (`NotAuthorizedException: Refresh Token has expired`), so even `test_harness.py` could not reach the API. Task group 5 in the archived change lists the four checks.
- **`test_harness.py` is stale: it reads `user_id` from `.credentials.json`, which now holds `email` / `access_token` / `id_token` / `refresh_token`.** It exits before doing anything useful. Fix the key names (and refresh the token per the README's reCAPTCHA step) before relying on it.
- **All five files in `openspec/specs/` fail `openspec validate --specs`** for a missing `## Purpose` section. Pre-existing and repo-wide as of 2026-09-06, so a failing spec validation is not necessarily caused by your change — check whether the error is only the Purpose one before chasing it.
- **TODO — verification debt from `fix-cognito-signin` (v0.4.4 shipped without on-device checks, maintainer decision 2026-11-07).** The Cognito direct sign-in was verified only by the automated suite (stdlib API tests and pytest config-flow tests) and the README token was checked in Firefox and Chromium; no sign-in reached the live service from Home Assistant. When there is time for a reinstall: (1) add the integration from scratch with a README token and confirm sensors populate; (2) a wrong password must return to the email/password form with `invalid_credentials` and Cognito's reason, and a token older than 2 minutes must stay on the token step with `token_rejected`; (3) trigger a reauth and confirm it succeeds (with a keg fitted, this also clears the Keg Freshness TODO above). Details in the archived change's `tasks.md`, section "Deferred".
- **TODO — verification debt from `add-keg-48180` and `add-oktoberfest-keg-art` (card 0.4.4 and 0.4.5 shipped without on-device checks, maintainer decisions 2026-11-07).** Do it together with the `fix-cognito-signin` checks above, on integration and card 0.4.5 or later: confirm the card editor's beer picker shows artwork for Camden Stout, Löwenbräu Oktoberfestbier and Spaten Oktoberfestbier, and that the two Oktoberfest images are sharp in the `hero` layout. With a 48180 keg fitted, confirm the Keg sensor reads "Camden Stout" and the card brands it. With a 29745 keg fitted, the sensor must read "Löwenbräu Oktoberfestbier" (with umlauts).
- **TODO — main specs fail `openspec validate --specs --strict` (all 5, pre-existing; seen 2026-11-07).** None of `openspec/specs/*/spec.md` has the `## Purpose` / `## Requirements` headers the current CLI requires; requirements start directly at `### Requirement:`. Archiving still works, but sync tooling and validation expect the headers. Fix in one housekeeping commit: add a short `## Purpose` and a `## Requirements` heading to each spec, then re-run strict validation.
- **Every main spec needs `## Purpose` above `## Requirements`** (OpenSpec 1.16 rejects specs without it; all five were back-filled 2026-11-08). A new capability gets its Purpose from the delta's `## Purpose` at archive; check `openspec validate --specs` passes after every sync.
- **TODO — two main specs still fail `openspec validate --specs --strict`** on requirement text over 500 characters (a warning, so plain validation passes): `api-client` "Sign-in with reCAPTCHA token" and `entities` "Keg name sensor". Split each into single-behavior requirements in a change made for that purpose, keeping every scenario; do not trim them inside an unrelated change.
- **TODO — own OpenSpec change: persist Cognito-refreshed tokens back to the config entry.** `PerfectDraftApiClient.refresh_access_token()` updates `_access_token`/`_id_token` in memory only, so every HA restart reloads the stale access token and burns a wasted 401-plus-refresh round trip before the first successful poll. Harmless today because the refresh token is what actually gates reauth and Cognito's `REFRESH_TOKEN_AUTH` never issues a new one, so nothing is lost — just wasteful. Deferred out of `fix-reauth-flow` to keep that diff surgical.
- **TODO — housekeeping, after `fix-cognito-signin` / `add-keg-48180` ship: take the GitHub token out of the `github` remote URLs** in both this repo and `Hassio-PerfectDraftPro-Component`. Not a leak (never committed; `.git/` is untracked), but `git remote -v` prints it. Order matters: first change `credential.helper` to an **absolute** path (`store --file=/home/rick/Lab/Dev/<repo>/.git/credentials`) — the current relative `.git/credentials` resolves against the worktree root, where `.git` is a file, so pushes from `.worktree/<topic>` only reach `github` (whose URL carries the token); pushing to `origin` from a worktree fails with "unable to open .git/credentials: Not a directory". Until fixed, push agent branches from the main checkout: `git push origin agent/<topic>` (no branch switch needed). Then strip the URL, run `git ls-remote github` from a worktree to prove auth, and update the `AGENTS.md` helper command to the absolute form.
- **Config-flow tests run in `.venv-test` (main checkout) on the system Python 3.14** with `pytest-homeassistant-custom-component==0.13.375` (core 2026.10.4). Run them from a worktree as `../../.venv-test/bin/pytest tests/`. Do not pin a harness that needs Python 3.12: there is no 3.12 and no C compiler on the dev host, so old numpy cannot build.
+1 -1
View File
@@ -1,7 +1,7 @@
{
"domain": "perfectdraft",
"name": "PerfectDraft",
"version": "0.4.5",
"version": "0.4.6",
"documentation": "https://github.com/Falkvinge/hassio-integration-perfectdraft-pro",
"issue_tracker": "https://github.com/Falkvinge/hassio-integration-perfectdraft-pro/issues",
"codeowners": ["@Falkvinge"],
@@ -0,0 +1,70 @@
{
"config": {
"step": {
"user": {
"title": "Compte PerfectDraft",
"description": "Entrez vos identifiants de l'application PerfectDraft.",
"data": {
"email": "Adresse e-mail",
"password": "Mot de passe"
}
},
"token": {
"title": "Jeton de vérification",
"description": "Collez le jeton de vérification depuis le site PerfectDraft. Consultez les [instructions d'installation](https://github.com/Falkvinge/hassio-integration-perfectdraft-pro#step-2-verification-token) pour le guide pas à pas de 30 secondes. Le jeton expire en 2 minutes, générez-le juste avant de le coller.",
"data": {
"recaptcha_token": "Jeton de vérification"
}
},
"reauth_confirm": {
"title": "Réauthentification PerfectDraft",
"description": "Votre session a expiré. Veuillez saisir à nouveau vos identifiants.",
"data": {
"email": "Adresse e-mail",
"password": "Mot de passe"
}
}
},
"error": {
"invalid_auth": "Échec de l'authentification : {reason}. Réessayez avec un nouveau jeton.",
"invalid_credentials": "PerfectDraft a rejeté l'adresse e-mail ou le mot de passe : {reason}.",
"token_rejected": "PerfectDraft a rejeté le jeton de vérification : {reason}. Générez un nouveau jeton et collez-le sous 2 minutes.",
"cannot_connect": "Impossible de se connecter au service PerfectDraft.",
"unknown": "Une erreur inattendue s'est produite."
},
"abort": {
"already_configured": "Ce compte PerfectDraft est déjà configuré.",
"reauth_successful": "Réauthentification réussie.",
"reauth_account_mismatch": "Ces identifiants correspondent à un autre compte PerfectDraft. Réauthentifiez-vous avec le compte initial de cette intégration, ou supprimez l'intégration et ajoutez l'autre compte séparément.",
"already_in_progress": "La configuration pour ce compte PerfectDraft est déjà en cours. Terminez ou annulez la configuration en attente dans Paramètres > Appareils et services."
}
},
"entity": {
"sensor": {
"temperature": { "name": "Température" },
"keg_remaining": { "name": "Niveau du fût" },
"keg_product_id": { "name": "ID du fût" },
"keg_name": { "name": "Fût" },
"connection": { "name": "Connexion" },
"door": { "name": "Porte" },
"pours": { "name": "Tirages" },
"last_pour": { "name": "Dernier tirage" },
"firmware": { "name": "Firmware" },
"mode": { "name": "Mode" },
"keg_freshness": { "name": "Fraîcheur du fût" }
},
"button": {
"mark_keg_changed": { "name": "Marquer le fût changé" }
}
},
"options": {
"step": {
"init": {
"title": "Options PerfectDraft",
"data": {
"scan_interval": "Intervalle d'actualisation (secondes)"
}
}
}
}
}
@@ -0,0 +1,2 @@
schema: spec-driven
created: 2026-11-07
@@ -0,0 +1,35 @@
## Context
PR #14 is one commit, `704f55e` by aurel <aurelien.ruat@hotmail.fr>, whose parent is the current `master` head (`851ec3a`). GitHub reports it mergeable with no conflicts. Checked before this change:
- `fr.json` has exactly the key set of `strings.json` and `en.json`, which also match each other.
- Every `{reason}` placeholder and the README link in the token step are carried over.
- The full suite passes on the PR branch: 77 tests, 587 subtests, including the new `test_translations.py`.
`git fetch github pull/14/head` makes the commit available locally.
## Goals / Non-Goals
**Goals:**
- Ship the contribution byte-for-byte, with aurel as the commit author, and have GitHub show PR #14 as merged.
**Non-Goals:**
- Editing the French wording or the contributed test (style, unittest vs pytest, hardcoded `("en", "fr")`).
## Decisions
**Merge the original commit, not a squash or a re-applied diff.** The worktree branch `agent/add-french-translation` starts at `master` and fast-forwards to `704f55e`; the version bump is a separate maintainer commit on top. When the branch is later merged into `master` and pushed to `github`, `704f55e` is reachable from the PR's base branch, so GitHub marks PR #14 merged and attributes the commit to aurel. Squashing or cherry-picking would change the hash, lose that link, and need a manual PR close.
**Integration-only patch release (0.4.6).** The card has no translation files, so it is unchanged. The versioning rule in `PROJECT_HYGIENE.md` allows a diverging patch.
**Keep the test strict.** Home Assistant falls back to English for missing keys, so partial translations would work at runtime. The maintainer chose exact parity instead, so French never falls silently behind. The cost is one more file to touch per string change, recorded in `PROJECT_HYGIENE.md`.
## Risks / Trade-offs
- [A future agent adds a string to `strings.json` and `en.json` only] → The test fails in that change; the `PROJECT_HYGIENE.md` note tells the agent to write the French entry rather than relax the test.
- [The new strings are shown on a narrow UI and truncate] → Not seen in testing, and the contributor runs it live. Fix in a follow-up only if a user reports it.
- [No on-device check on the dev host] → As with 0.4.4 and 0.4.5, there is no Home Assistant on the dev host. The contributor's own instance is the live check; the static checks above cover the files.
## Migration Plan
None. Updating via HACS and restarting Home Assistant picks up `fr.json`. Rollback is reinstalling 0.4.5.
@@ -0,0 +1,34 @@
## Why
[PR #14](https://github.com/Falkvinge/hassio-integration-perfectdraft-pro/pull/14) from @Aurel004 (aurel) adds a complete French translation, so French-language Home Assistant installs show the config flow, errors and entity names in French instead of English. The contributor runs it on his own instance and checked the AI-generated strings by hand; the maintainer had a native French speaker look at it too. It is a first contribution, so it ships exactly as submitted, with his authorship kept.
## What Changes
- Merge the PR's single commit (`704f55e`, authored by aurel) unchanged. It adds:
- `custom_components/perfectdraft/translations/fr.json`, covering every key in `strings.json`.
- `tests/test_translations.py`, which fails when `en.json` or `fr.json` has a different key structure from `strings.json`.
- No wording edits. "Marquer le fût changé" stays as submitted; it is correct, and shorter text suits the button label.
- Bump the integration to 0.4.6. The card has no translations and stays at 0.4.5, which the versioning rule allows (shared major.minor, patch may diverge).
- Record in `PROJECT_HYGIENE.md` that from now on every new or renamed UI string needs an English and a French entry, because the new test enforces exact key parity.
- Release v0.4.6 crediting @Aurel004.
Not in scope:
- Translated entity states or attributes. `strings.json` defines none, so there is nothing to translate.
- Other languages, or loosening the parity test to allow partial translations.
## Capabilities
### New Capabilities
None.
### Modified Capabilities
- `hacs-packaging`: the "Translations" requirement covers English only. It now also requires a French translation and exact key parity between `strings.json` and every shipped translation file.
## Impact
- Users with Home Assistant set to French see French labels after updating. Existing entity IDs are kept in the entity registry and don't change; only display names do. Everyone else is unaffected.
- Contributors and agents: any change to `strings.json` must update `translations/en.json` and `translations/fr.json` in the same commit, or `tests/test_translations.py` fails.
- Files: `custom_components/perfectdraft/translations/fr.json` (new), `tests/test_translations.py` (new), `custom_components/perfectdraft/manifest.json` (version), `PROJECT_HYGIENE.md` (main checkout).
@@ -0,0 +1,19 @@
## MODIFIED Requirements
### Requirement: Translations
The integration SHALL provide English and French UI strings for all config flow steps, errors, abort reasons, options, and entity names. Every shipped translation file SHALL have exactly the same key structure as `strings.json`.
#### Scenario: Translation files
- **WHEN** HA renders the integration UI
- **THEN** `strings.json` and `translations/en.json` SHALL provide labels for all steps, fields, errors, and entity names
- **THEN** descriptions SHALL not contain curly braces (parsed as translation placeholders) or newlines (cause MALFORMED_ARGUMENT)
#### Scenario: French UI
- **WHEN** HA renders the integration UI with its language set to French
- **THEN** `translations/fr.json` SHALL provide French labels for all steps, fields, errors, abort reasons, options, and entity names
- **THEN** each French string SHALL use the same `{placeholder}` names as its English counterpart
#### Scenario: Key parity
- **WHEN** a key is added to, renamed in, or removed from `strings.json`
- **THEN** `translations/en.json` and `translations/fr.json` SHALL be updated to the same key structure in the same change
- **THEN** the test suite SHALL fail if any of the three files has a key the others lack
@@ -0,0 +1,23 @@
## 1. Worktree and contribution
- [x] 1.1 `scripts/agent-worktree.sh create add-french-translation`; verify `.worktree/add-french-translation/.agent-lock` exists and `git worktree list` shows branch `agent/add-french-translation` at `master`
- [x] 1.2 `git fetch github pull/14/head`, then put the worktree branch on `704f55e5958717899fea2265f1a3c627dd4cde9d`; verify `git log -1 --format='%H %an'` shows `704f55e…` by aurel and `git diff 851ec3a --stat` lists only `translations/fr.json` and `tests/test_translations.py`
- `master` had moved on by the proposal commit (`2050051`, `openspec/` only), so `--ff-only` was impossible. The fresh branch had no commits of its own, so it was reset to `704f55e` (parent `851ec3a`) instead; the commit is unchanged. Diff vs `851ec3a`: the two files, 109 insertions
- [x] 1.3 Verify the contribution against the spec: `fr.json` key set equals `strings.json`, and every string uses the same `{placeholder}` names as `strings.json`; then `../../.venv-test/bin/pytest tests/` from the worktree passes, including `test_translations.py`
- 34 keys match, no placeholder mismatches; 77 passed, 587 subtests passed
## 2. Version
- [x] 2.1 Bump `custom_components/perfectdraft/manifest.json` to 0.4.6 and commit as the maintainer; verify `git diff HEAD~1` is the single version line and the full suite still passes. Record the commit hash here
- Commit `9a81654` on `agent/add-french-translation`, on top of `704f55e`; one-line diff; 77 passed, 587 subtests passed
## 3. Project hygiene
- [x] 3.1 Add a line to `PROJECT_HYGIENE.md` section 11 (main checkout): every new, renamed or removed key in `strings.json` must be mirrored in `translations/en.json` and `translations/fr.json` in the same commit, with a French string written rather than an English placeholder or a relaxed test; `tests/test_translations.py` enforces it. Commit in the main checkout; verify with `git log -1 -- PROJECT_HYGIENE.md`
## Workflow follow-up
- Archive per `AGENTS.md`: merge `agent/add-french-translation` into `master` with `--no-ff` (keeps `704f55e` intact), push `master` to `origin` and `github`, sync the `hacs-packaging` delta into `openspec/specs/`, archive, remove the worktree and branch.
- After the push, confirm via the GitHub API that PR #14 reports `merged: true`. If it doesn't, close it with a comment linking the merge commit.
- Tag `v0.4.6` and publish the GitHub release "v0.4.6 — French translation" in the format of v0.4.5: French UI for setup, errors and entity names; thanks to @Aurel004 for [#14](https://github.com/Falkvinge/hassio-integration-perfectdraft-pro/pull/14); note that the card stays at 0.4.5, no breaking changes, no re-configuration.
- Comment on PR #14 with a thank-you and the release link.
+4
View File
@@ -1,3 +1,7 @@
## Purpose
The async client for PerfectDraft's cloud services and the integration's only point of contact with them. It signs in through AWS Cognito with the account's email, password and a reCAPTCHA verification token, refreshes the session without user involvement, and fetches the account's machines and their telemetry from `api.perfectdraft.com`.
## Requirements
### Requirement: Async HTTP client
+4
View File
@@ -1,3 +1,7 @@
## Purpose
The Home Assistant UI flows that connect a PerfectDraft account: initial setup with email, password and a browser-generated verification token; reauthentication when the session can no longer be refreshed; and an options form for the polling interval. Failures tell the user which input was rejected and why.
## Requirements
### Requirement: User step collects email and password
+4
View File
@@ -1,3 +1,7 @@
## Purpose
Polls the PerfectDraft API once per interval for each configured account and shares the result with every entity, so request volume stays low enough to avoid the API's rate limiting. It also turns API failures into Home Assistant's reauth and unavailable states.
## Requirements
### Requirement: Single DataUpdateCoordinator per config entry
+4
View File
@@ -1,3 +1,7 @@
## Purpose
The Home Assistant device and entities that represent a PerfectDraft machine on dashboards and in automations: beer temperature, keg level, the fitted keg and its beer name, machine status, pour data, and a client-side keg freshness countdown with a manual keg-change button.
## Requirements
### Requirement: HA Device per PerfectDraft machine
+15 -1
View File
@@ -1,3 +1,7 @@
## Purpose
The repository layout, metadata, branding, documentation and UI strings that let the integration be installed and updated through HACS and presented properly in Home Assistant, in English and French.
## Requirements
### Requirement: HACS-compliant repository structure
@@ -51,9 +55,19 @@ The repository SHALL be mirrored to GitHub for HACS compatibility, since HACS re
- **THEN** they SHALL be pushed to both the primary Gitea repo (origin) and the GitHub mirror (github)
### Requirement: Translations
The integration SHALL provide English UI strings for all config flow steps, errors, abort reasons, options, and entity names.
The integration SHALL provide English and French UI strings for all config flow steps, errors, abort reasons, options, and entity names. Every shipped translation file SHALL have exactly the same key structure as `strings.json`.
#### Scenario: Translation files
- **WHEN** HA renders the integration UI
- **THEN** `strings.json` and `translations/en.json` SHALL provide labels for all steps, fields, errors, and entity names
- **THEN** descriptions SHALL not contain curly braces (parsed as translation placeholders) or newlines (cause MALFORMED_ARGUMENT)
#### Scenario: French UI
- **WHEN** HA renders the integration UI with its language set to French
- **THEN** `translations/fr.json` SHALL provide French labels for all steps, fields, errors, abort reasons, options, and entity names
- **THEN** each French string SHALL use the same `{placeholder}` names as its English counterpart
#### Scenario: Key parity
- **WHEN** a key is added to, renamed in, or removed from `strings.json`
- **THEN** `translations/en.json` and `translations/fr.json` SHALL be updated to the same key structure in the same change
- **THEN** the test suite SHALL fail if any of the three files has a key the others lack
+39
View File
@@ -0,0 +1,39 @@
"""Verify that translation files match strings.json key structure."""
import json
from pathlib import Path
import unittest
COMPONENT_DIR = Path(__file__).parent.parent / "custom_components" / "perfectdraft"
def _key_paths(obj, prefix=""):
paths = set()
if isinstance(obj, dict):
for k, v in obj.items():
full = f"{prefix}.{k}" if prefix else k
if isinstance(v, dict):
paths |= _key_paths(v, full)
else:
paths.add(full)
return paths
class TestTranslations(unittest.TestCase):
def test_en_and_fr_match_strings_json_keys(self):
strings = json.loads(
(COMPONENT_DIR / "strings.json").read_text(encoding="utf-8")
)
expected = _key_paths(strings)
for lang in ("en", "fr"):
with self.subTest(lang=lang):
data = json.loads(
(COMPONENT_DIR / "translations" / f"{lang}.json").read_text(
encoding="utf-8"
)
)
self.assertEqual(_key_paths(data), expected)
if __name__ == "__main__":
unittest.main()