cancervariants / cancervariants/variation-normalization
Look into using vrs-python for VCF translation
Open
priority:high
technical debt
- Dominant language
- Python
- Stars
- 15
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I initially did not use [_from_gnomad](https://github.com/ga4gh/vrs-python/blob/main/src/ga4gh/vrs/extras/translator.py#L133) from vrs-python's translator since we tokenize, classify, validate, then translate for toVRS and normalize. I'm wondering if for VAI (+ possible performance purposes), we should use this method to go straight to the VRS object. We could do this in a separate endpoint or refactor the current structure.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.