Resolve variant vep consequence per context discrepancy #1724
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.