Add overview support and emitter display names to spec-dashboard#9891
Merged
timotheeguerin merged 3 commits intomicrosoft:mainfrom Mar 4, 2026
Merged
Conversation
Contributor
|
No changes needing a change description found. |
bef713f to
d90c59f
Compare
Collaborator
|
You can try these changes here
|
3318ec1 to
3cbdd15
Compare
timotheeguerin
approved these changes
Mar 4, 2026
- Add showOverview option and coverage overview component - Add emitterDisplayNames option for friendly column headers - Extract coverage utility functions - Refactor dashboard table to use display names Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
3cbdd15 to
112f347
Compare
timotheeguerin
approved these changes
Mar 4, 2026
Open
15 tasks
github-merge-queue bot
pushed a commit
to Azure/typespec-azure
that referenced
this pull request
Mar 4, 2026
## Summary Configures the Can I Use HTTP dashboard to use the new spec-dashboard features added in [microsoft/typespec - feature/spec-dashboard-overview](https://github.com/joheredi/typespec/tree/feature/spec-dashboard-overview): - **Coverage Overview** — Shows per-emitter coverage percentage cards at the top of the dashboard - **Emitter Display Names** — Maps package names to friendly labels (e.g., `@azure-tools/typespec-python` → `Python`) - **Scenario Tiers** — Adds tier-based filtering with Core and Backlog categories ### Changes | File | Description | |------|-------------| | `core` | Updated submodule to include spec-dashboard overview support | | `website/src/pages/can-i-use/http.astro` | Added `showOverview`, `emitterDisplayNames`, and `tiers` configuration | | `website/src/pages/can-i-use/scenario-tiers.ts` | **New** — Scenario tier definitions (Core / Backlog) | ### Dependencies This PR depends on the core submodule PR: microsoft/typespec#9891 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add overview support and emitter display names to spec-dashboard
Summary
This PR adds two new configuration options to the
spec-dashboardpackage to improve the coverage dashboard UX:showOverview— Renders coverage overview cards at the top of the dashboard, showing per-emitter coverage percentages at a glance.emitterDisplayNames— Allows consumers to provide friendly display names for emitter columns (e.g.,@azure-tools/typespec-python→Python) instead of relying on generator metadata or raw package names.Changes
apis.tsshowOverviewandemitterDisplayNamesoptional fields toCoverageFromAzureStorageOptionscoverage-overview.tsxCoverageOverviewcomponent that aggregates coverage across all summaries and renders a responsive grid of per-emitter cards with color-coded percentagescoverage-utils.tsgetCompletedRatioutility for reuse across componentsdashboard.tsxCoverageOverviewwhenshowOverviewis enableddashboard-az-storage.tsxDashboarddashboard-table.tsxemitterDisplayNames; usedisplayName ?? report?.generatorMetadata?.name ?? languagefallback chain for column headers; removed inlinedgetCompletedRatioin favor of the shared utilityDisplay Name Resolution
Column headers now follow this priority:
emitterDisplayNames[packageName](if provided)report.generatorMetadata.name(from coverage data)