Where and how to define the `data_proxy` interface
- Dominant language
- Python
- Stars
- 62
- Forks
- 42
- Avg merge
- 1h 2m
- Merged PRs (30d)
- 1
Description
https://github.com/ga4gh/vrs-python/blob/main/src/ga4gh/vrs/dataproxy.py (always a tell when the code references "VR" and not "VRS")
Most of this is copy-pasted from SeqRepo. This seems less than ideal, but I think we probably didn't want to depend on SeqRepo for the dataproxy if it could be avoided.
* Is that still necessary? Can't we install SeqRepo and just use some of the API library, not the actual data?
* ~What about refget? It looks... a lot like the dataproxy API, and it's a GA4GH thing. Can we just define a refget API? Seqrepo-rest-server already provides refget output IIRC~ from what I hear refget is missing something that we expect from the dataproxy regarding alias lookup
* Can we just define it once in a central location and have both SeqRepo and VRS Python import it?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.