Skip to content

fix(dashboards): rename lineage field to outbreakLineage and update values - #1360

Merged
fhennig merged 1 commit into
mainfrom
mpox-outbreak-lineage-update
Jul 29, 2026
Merged

fix(dashboards): rename lineage field to outbreakLineage and update values#1360
fhennig merged 1 commit into
mainfrom
mpox-outbreak-lineage-update

Conversation

@fhennig

@fhennig fhennig commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Pathoplexus restructured mpox lineages: the LAPIS field is now outbreakLineage (old lineage field no longer has a lineage index, causing the lineage definition fetch to fail). Lineage values are now prefixed with the outbreak identifier (e.g. sh2017/F.1).

  • Labels updated to "Outbreak & Lineage" throughout
  • Predefined variants and compare-side-by-side defaults updated to use sh2017/F.* values
  • E2E test helper updated with new field placeholder and lineage value

Pathoplexus restructured mpox lineages: the LAPIS field is now
`outbreakLineage` (old `lineage` field no longer has a lineage index,
causing the lineage definition fetch to fail). Lineage values are now
prefixed with the outbreak identifier (e.g. `sh2017/F.1`).

- Labels updated to "Outbreak & Lineage" throughout
- Predefined variants and compare-side-by-side defaults updated to
  use `sh2017/F.*` values
- E2E test helper updated with new field placeholder and lineage value

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@fhennig fhennig self-assigned this Jul 29, 2026
@vercel

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
dashboards Ready Ready Preview, Comment Jul 29, 2026 8:45am

Request Review

@fhennig fhennig changed the title fix(mpox): rename lineage field to outbreakLineage and update values fix(dashboards): rename lineage field to outbreakLineage and update values Jul 29, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the mpox dashboard configuration to align with Pathoplexus’ new lineage data model by switching the LAPIS lineage field from lineage to outbreakLineage and updating default/predefined lineage values and UI labels accordingly.

Changes:

  • Switched mpox lineage LAPIS field to outbreakLineage.
  • Updated mpox lineage placeholders/labels to “Outbreak & Lineage”.
  • Updated mpox predefined variants and compare-side-by-side defaults to use outbreak-prefixed values (e.g. sh2017/F.1), plus aligned the E2E helper values.

Reviewed changes

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

File Description
website/src/views/mpox.ts Renames the mpox lineage LAPIS field to outbreakLineage and updates placeholders, chart label, and default/predefined lineage values.
website/tests/helpers/organisms.ts Updates mpox E2E helper placeholder and lineage value to match the new “Outbreak & Lineage” filter and outbreak-prefixed lineage format.

@fhennig
fhennig merged commit da9e6b6 into main Jul 29, 2026
14 checks passed
@fhennig
fhennig deleted the mpox-outbreak-lineage-update branch July 29, 2026 09:01
fhennig added a commit that referenced this pull request Jul 29, 2026
…alues (#1360)

Pathoplexus restructured mpox lineages: the LAPIS field is now
`outbreakLineage` (old `lineage` field no longer has a lineage index,
causing the lineage definition fetch to fail). Lineage values are now
prefixed with the outbreak identifier (e.g. `sh2017/F.1`).

- Labels updated to "Outbreak & Lineage" throughout
- Predefined variants and compare-side-by-side defaults updated to use
`sh2017/F.*` values
- E2E test helper updated with new field placeholder and lineage value

Co-authored-by: Felix Hennig <felix-agent@felixhennig.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
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.

3 participants