Skip to content

Resolve variant vep consequence per context discrepancy #1724

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rileyhgrant
Copy link
Contributor

Resolves #1723

Adds a filter to the getConsequence helper for the Region context to filter Transcript Consequences in the same way that the Gene page already does. This makes the reporting of VEP consequences consistent across the various page contexts.


Brief background, see the issue for more complete context:

Based on context (Gene vs Region vs Variant), differing filters are applied to the Transcript Consequences field in the API. This results in reporting of different consequences based on which page a user is viewing.

In the case of APEH, there are two variants that are reported as having only intronic consequences on both the Gene and individual Variant pages, but are reported as having coding consequences (Synonymous and Missense) on the Region page.

@rileyhgrant rileyhgrant self-assigned this May 6, 2025
@rileyhgrant rileyhgrant changed the title Resolve Variant consequence discrepancy based on Consequence Resolve variant vep consequence per context discrepancy May 6, 2025
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.

Displayed VEP consequence differs based on context (Gene/Region/Variant)
1 participant