Story: Badges to database (phase 1)
Table of Contents
This page documents a story in Sprint 15. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Replace hardcoded Qt UI badge metadata with database-driven definitions so Qt + Wt can share the same source of truth. Phase 1 lands the infrastructure.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 15 |
| Now | Completed 2026-03-28. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2026-03-28 |
Acceptance
- Codegen models for badge_severity, code_domain, badge_definition, badge_mapping junction.
- Generated SQL + C++ artefacts integrated.
- Population seed data extracted from hardcoded colours.
- BadgeCache in ores.qt wired into client startup.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Badges to database (phase 1 infrastructure) | DONE | 2026-05-20 | 2026-03-28 | Codegen models for badge_severity + code_domain + badge_definition + badge_mapping junction; integrate generated SQL + C++ artefacts; population seed data from hardcoded colours; BadgeCache in ores.qt wired into client startup. Foundation that lets Wt reuse the same metadata. |
Decisions
- DB-driven over hardcoded
- lets Wt consume the same metadata without re-encoding everything.
Out of scope
- Wt consumption of badge metadata (phase 2).
- User-editable badge definitions (phase 3).
See also
None.