feat(editor): multilingual editor 2/3 — Columns view of a translation, Translate element, element form with source values #202
No reviewers
Labels
No labels
bug
enhancement
needs-triage
ready-for-agent
ready-for-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/deckle!202
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "afk/199"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #199
Second editor slice of the multilingual work (PRD #192 §8, mockup
docs/mockups/multilingual/). Engine untouched; everything rides the existing API ("Translations on the wire").Columns view of a connected translation
translation.changed. The engine hashes items separately, so a Cards element whose card changed is marked too.GET /api/pagein the default language, held by the page editor assourceData()) is walked per slot or container (web/src/translationgrid.ts, pure and unit-tested). Placeholders show for top-most untranslated elements only.POST /api/element/translate, then the form opens; a 409 shows the server's message) and a ⋮ menu (Translate / Open element / Leave untranslated).[autoland] verdict: pass
PASS — validated by the autoland lander.
Signal:
labctl pr checks 202aggregate success (ci / build-and-test, 14m20s: npm ci/build/test, go vet, go test incl. the skills and AGENTS.md drift tests, go build). Not re-run locally.Conventions: Conventional Commits title;
Closes #199present; branch is current with main (merge-base = origin/main), no conflicts.Scope matches #199: Columns view of a connected translation (web/src/translationgrid.ts, LayoutGrid/TranslationPlaceholder), banners (PageBanner.tsx), the element form's source-value boxes, items rules and synced Appearance (ElementForm.tsx, SourceValue.tsx, FormScreen.tsx), the delete plan (ElementDeleteDialog.tsx), and the address-based preview map (previewmap.ts), which the issue asked to be checked. The fixture change (services/_index.de.md connected, cards/card sidecars) is what the acceptance criteria need. The four Go test expectations that changed follow from that fixture. Existing web tests are unmodified apart from one widened import in translateApi.test.ts. Skills and AGENTS.md are rightly left alone: AGENTS.md "Translations" already covers Translate element/all and the change mark, and no skill walks through editor screens on a translation.
Note (non-blocking, disclosed in the PR): the walk through the UI in a browser against the mockup has not been done.