Fix issue with missing INFO field due to '=' in annotation field#8
Open
pzweuj wants to merge 1 commit into
Open
Fix issue with missing INFO field due to '=' in annotation field#8pzweuj wants to merge 1 commit into
pzweuj wants to merge 1 commit into
Conversation
Resolved a parsing error where annotations containing '=' caused INFO fields to be inaccessible. This fix ensures that INFO fields are correctly extracted regardless of annotation content.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resolved a parsing error where annotations containing '=' caused INFO fields to be inaccessible. This fix ensures that INFO fields are correctly extracted regardless of annotation content.
This bug occurs because VEP may add annotations with "=" symbols, like in HGVSp for synonymous mutations. When this happens, the INFO field in the parsed dictionary gets set to True instead of the expected value. As a result, when we later try to use split("|") on the INFO content, it fails because the data isn’t in the expected format.