Annotated Variant Export #380
Open
Conversation
This file contains 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
bencap
force-pushed
the
feature/bencap/356/va-spec-variant-export
branch
2 times, most recently
from
e70ec3e to
d320b9d
Compare
This was
linked to
issues
Feb 13, 2025
bencap
force-pushed
the
feature/bencap/356/va-spec-variant-export
branch
from
f5c63f5 to
d224bc0
Compare
|
Tests will fail until Cat-VRS update. |
Bumps the following core dependencies: - Python: 3.9 -> 3.11 - Pydantic 1.10.18 -> 2.10.4 - FastAPI: 0.95.2 -> 0.115.6 - Starlette: 0.27.0 -> 0.41.3 This list is not close to extensive, and other packages were updated as well for compatibility; Please see the `poetry.lock` diff.
bencap
force-pushed
the
feature/bencap/356/va-spec-variant-export
branch
from
d224bc0 to
c943363
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
VA-Spec implementation for MaveDB mapped variant objects. VA-Spec depends on Pydantic 2.0+, which depends on Python 3.11+, so this change also bumps certain core dependencies to retain compatibility.
VA-Spec objects can be exported via a new dedicated endpoint. Objects are constructed according to VA-Spec documentation and core information model. For more information about the VA-Spec core information model, see their documentation.
An example VA-Spec object for a variant from https://mavedb.org/score-sets/urn:mavedb:00000097-a-1 is attached: va-spec_example_variant.json