feat(components): add per-mutation name/description overrides to MutationAnnotation

[fhennig]

Closes #1120

Summary

• Entries in nucleotideMutations, aminoAcidMutations, nucleotidePositions, and aminoAcidPositions can now be a plain string or an object with optional name/description fields that override the group-level annotation values in the popup
• Overrides are resolved eagerly at index-build time in buildAnnotationIndex, so no extra work happens at render time
• Plain string arrays remain valid — fully backward compatible at runtime

Example

{
  "name": "3CLpro inhibitor resistance",
  "description": "Mutations affecting 3CLpro drug binding",
  "symbol": "c",
  "nucleotideMutations": [
    { "mutation": "ORF1a:T2343C", "name": "3CLpro:T31C", "description": "Disrupts nirmatrelvir binding" },
    "ORF1a:G2558A"
  ]
}

Annotation type change

The TypeScript types for the four list fields change from string[] to (string | { mutation/position: string; name?: string; description?: string })[]. Consumers passing plain string arrays are unaffected at runtime; only strict TypeScript type checks would surface a difference.

Test plan

• All 211 existing tests pass
• New MutationWithPerMutationInfoOverride story covers the override path

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboard-components	Ready	Preview, Comment	Jun 8, 2026 1:56pm

[Copilot]

Pull request overview

Adds support for per-mutation (and per-position) name/description overrides in mutation annotations, resolving those overrides eagerly when building the annotation lookup index so UI rendering remains simple and backward compatible with existing string-only configs.

Changes:

• Extend the mutation annotation schema/types to allow list entries to be either strings or { mutation/position, name?, description? } objects.
• Build a resolved annotation index (ResolvedMutationAnnotation) at provider setup time and update consumers to render resolved names/descriptions.
• Add story + unit tests covering the override behavior.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
components/src/web-components/mutationAnnotations.mdx	Documents the new per-entry override shape and provides an example.
components/src/web-components/mutation-annotations-context.ts	Updates Zod schema/types to accept per-entry override objects.
components/src/web-components/gs-app.ts	Updates public prop typings and JSDoc to reflect new entry shapes.
components/src/preact/MutationAnnotationsContext.tsx	Builds an indexed lookup with resolved per-entry name/description overrides.
components/src/preact/MutationAnnotationsContext.spec.tsx	Updates expectations for resolved outputs and adds override-focused tests.
components/src/preact/components/annotated-mutation.tsx	Renders resolved title/description in the annotation modal.
components/src/preact/components/annotated-mutation.stories.tsx	Adds a story to demonstrate per-mutation override display.
components/src/preact/mutationsOverTime/getFilteredMutationCodes.ts	Adapts filtering to the new resolved annotation shape.
components/src/preact/mutationsOverTime/getFilteredMutationCodes.spec.ts	Updates tests to build the new annotation index before filtering.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[fengelniederhammer]

Breaking change

The TypeScript types for the four list fields change from string[] to (string | { mutation/position: string; name?: string; description?: string })[]. Consumers passing plain string arrays are unaffected at runtime; only strict TypeScript type checks would surface a difference.

This isn't really breaking, is it?

[fengelniederhammer]

• what Copilot said

[Copilot]

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.