Skip to content

refactor: Rename Variant → AssayedVariant and MappedVariant → MappingRecord #745

@bencap

Description

@bencap

Context

⚠️ Deferred — do not schedule until the DerivedAllele feature is stable.

The current naming obscures the semantic role of each entity. With DerivedAllele added, the full chain is:

  • What the assay measured → Variant (clearer as: AssayedVariant)
  • How it maps to a reference → MappedVariant (clearer as: MappedAllele)
  • What nucleotide variants it implies → DerivedAllele

Goal

Rename VariantAssayedVariant and MappedVariantMappedAllele across the API codebase as a single atomic refactor. This is a large surface area change — coordinate any breaking response field renames with UI and API consumers before executing.

Scope

  • SQLAlchemy model renames + Alembic migration for any table/column renames
  • All FK references updated
  • Router, endpoint parameter, and response schema renames
  • API response field names updated (breaking change — coordinate with UI and consumers)
  • All tests updated
  • OpenAPI spec updated

Metadata

Metadata

Assignees

No one assigned

    Labels

    app: backendTask implementation touches the backendapp: databaseTask implementation requires database changestype: maintenanceMaintaining this project

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions