Task: Classification column should use a badge
This page documents a task in the Currency pair support in reference data story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
The Currency Pairs list's Classification column (major / minor /
exotic / commodity) renders as plain text. Add a new classification
badge widget (colour-coded per tier) and use it in the list, following
the badge pattern used for book (clever_dijkstra worktree, not yet
merged).
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Currency pair support in reference data |
| Now | Nothing. |
| Waiting on | book badge widget precedent merging (clever_dijkstra worktree). |
| Next | Nothing. |
| Last touched | 2026-07-08 |
3. Acceptance
[ ]A new classification badge widget exists, styled consistently with the existing badge family.[ ]Classificationrenders as a badge in the Currency Pairs list for all four tiers (major/minor/exotic/commodity).
4. Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
5. Notes
6. PRs
| PR | Title |
|---|---|
7. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
8. Result
Delivered as part of PR #1472 (task DAE530F1). Classification renders
as a badge in the list and as a badge-styled combo in the detail
dialog. Colours went through two revisions after initial review: first
using RAG (green/amber/red) by mistake, then reused shared badges that
bled colour meaning into unrelated domains — settled on four dedicated,
clearly separated non-RAG hues (classification_major=/=_minor=/
=_exotic=/=_commodity — blue/teal/violet/sky). See
UX Language rule 3 and the new Badge Catalogue.