Skip to content

Extract VEP transcript-matching consequence logic into shared lib/vep/ #848

Description

@bencap

Move transcript-matching consequence resolution into variant-annotation's lib/vep/ as the shared implementation. Rewire api/src/mavedb/lib/vep.py to consume it and delete the api's duplicate VEP_CONSEQUENCES list.

Independent of RT.

Activity

  1. added this to the R2026.3 milestone on Aug 18, 2026
  2. added theissue type on Aug 18, 2026
  3. self-assigned this
    on Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app: backendTask implementation touches the backend

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions