Skip to content

feat: donut available on every bench + inline distribution row - #107

Merged
Flotapponnier merged 1 commit into
mainfrom
feat/donut-all-units-inline-distribution
May 23, 2026
Merged

feat: donut available on every bench + inline distribution row#107
Flotapponnier merged 1 commit into
mainfrom
feat/donut-all-units-inline-distribution

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator
  1. Donut partout : la vue donut était cachée hors des benches count. Maintenant disponible sur tous les units. Le switcher cache déjà les vues inapplicables, donc 'présente partout' = 'découvrable partout'.
  2. Distribution inline : la row [logo+name] + [value] était au-dessus du track, créant un creux blanc. Restructurée en grid 3 colonnes — logo+name | track | value — tout sur une seule ligne.

Donut everywhere
views.ts mapping previously gated donut to count benches only. Two
problems with that: (1) the option was invisible on the bench the
reader was looking at, (2) 'share of the field's total p50' is a
perfectly valid read on latency / cost / yield too, even if it's
unusual. Surface it on every unit and let the reader pick - the
switcher already hides views that don't apply, so always-present
just means always-discoverable.
Inline distribution layout
DistributionChart rendered name + value above the track and the
percentile markers below, eating ~40 px per row to a half-empty
header line. Restructured as a 3-column grid: [logo + name] [track]
[p50 value], all on one line. The track now sits flush with the
identity column so there's no white gap between the provider chip
and its bar. Mobile keeps the same single-line layout via a
narrower min-width on the identity column.
@Flotapponnier
Flotapponnier merged commit cc6e52f into mainMay 23, 2026
@Flotapponnier
Flotapponnier deleted the feat/donut-all-units-inline-distribution branch May 23, 2026 11:10
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@Flotapponnier