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
Parser().parse_any_variant does not parse any variant #167
Comments
Original comment by andrew_mcmurry (Bitbucket: andrew_mcmurry, GitHub: hyperfl0w): updated grammar to support parse_any_edit and parse_any_position can I please have commit access? |
Original comment by andrew_mcmurry (Bitbucket: andrew_mcmurry, GitHub: hyperfl0w):
|
Original comment by Reece Hart (Bitbucket: reece, GitHub: reece): As discussed in person, the intent of the any_variant rule was solely to parse strings of the form :.<arbitrary_text> . However, the SV returned from this is not very useful, or is at least confusing. I have commented out that rule from hgvs.pymeta until there is a well-defined need. commit edbf482e0774 |
Originally reported by: andrew_mcmurry (Bitbucket: andrew_mcmurry, GitHub: hyperfl0w)
Expected: parse_any_variant returns any variant type defined in the Grammar.
Actual: parse_any_variant is inherited method of the Parser construction and doesn't actually traverse the grammar.
Suspected Cause: parse_any_variant was accidentally included by inheritance.
The text was updated successfully, but these errors were encountered: