-
Notifications
You must be signed in to change notification settings - Fork 2
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
HGVS - reference validation now fails #491
Comments
@davmlaw Not quite sure what the intended output is here. NM_005629.3(SLC6A8):c.1403A= can be imported, matched and searched for but NM_018090.5:c.462= fails import and searching (error about not having a base) |
Fix was to allow creation of a reference HGVS, didn't work due to a bug. The error about not having a base is due to our enforcing that we specify the reference in our HGVSs - so that's the right behavior the example I listed was wrong and forgot about that rule |
NM_018090.5:c.462= in prod complains about Is this expected? |
Yeah I think we should just take the reference base here, if we want to stop people from doing that can always give a warning / flag etc but should resolve it Needs latest pyhgvs |
@davmlaw What has changed since your last comment? |
Fails due to https://github.com/SACGF/variantgrid_private/issues/2142 "NM_018090.5:c.462=" now fails with "Coordinate span (1) not equal to ref length 2" |
This was due to the HGVS library not handling reference variants without reference bases supplied - my validation change just exposed it Raised as bug counsyl/hgvs#61 I have fixed it in our version of HGVS library, so upgrade via:
|
James upgraded Shariant test - tested submitting "NM_018090.5:c.462=" works fine just raises a matching warning whne it inserts the gene symbol and reference base Search also works (not sure if it was broken before) |
Testing:
|
Searching or submitting classification for these now fails validating that = not in GATC - issue with validating our internal representation
NM_005629.3(SLC6A8):c.1403A=
NM_018090.5:c.462=
The text was updated successfully, but these errors were encountered: