Skip to content

Framework variants: two entries of one framework side by side - #1712

Open
nigrosimone wants to merge 3 commits into
MDA2AV:mainfrom
nigrosimone:framework-variants
Open

nigrosimone wants to merge 3 commits into
MDA2AV:mainfrom
nigrosimone:framework-variants

Conversation

@nigrosimone

@nigrosimone nigrosimone commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

From #1709. Two entries of one framework, like hono-node and hono-bun, are unrelated rows on the board today. This adds variants: same framework, another runtime or documented API. All variants are legitimate and it is separate from mode.

  • framework and variant in meta.json. scripts/check_variants.py allows at most two per framework, in its own small workflow.
  • Every variant has its row with a pill. A variant is hidden by default: it is listed only with the new Variants filter and has no badges or medals, unless it sets "default_visible": true.
  • hono-node and hono-bun are the first two variants.

A hidden variant still counts for the leader of each profile, like a tuned entry that is filtered out. I left out ?variant= for badges: each entry has already its own URL.

Tested with hono-bun hidden: check_badge_parity.js passes and fails without the change in badge_composite, the board in headless Chrome hides and shows the row with the filter, check_variants.py refuses the five wrong cases.

@nigrosimone
nigrosimone marked this pull request as ready for review November 5, 2026 18:11
@Kaliumhexacyanoferrat

Copy link
Copy Markdown
Collaborator

I feel „default_visible“ should be false if not explicitely specified 🤔

Otherwise we will probably see all the variants on top. I would start defensively here - we can change the default later at any time.

@nigrosimone

Copy link
Copy Markdown
Contributor Author

Good point, done. default_visible is now false if not specified, and only for variants. hono-node and hono-bun set it to true, so the board stays the same.

This branch has not been deployed

No deployments
Sign up for free to 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.

2 participants