Skip to content
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

use cat-vrs-python and va-spec-python #388

Closed
korikuzma opened this issue Jul 16, 2024 · 2 comments · Fixed by #404
Closed

use cat-vrs-python and va-spec-python #388

korikuzma opened this issue Jul 16, 2024 · 2 comments · Fixed by #404
Assignees
Labels
enhancement New feature or request priority:high High priority

Comments

@korikuzma
Copy link
Member

We currently store Cat VRS + VA-Spec Pydantic models in https://github.com/cancervariants/metakb/tree/staging/src/metakb/schemas. However, we are now separating these out into their respective Python packages. There have also been many breaking changes in these models which are updated in cat-vrs-python and va-spec-python. We should remove the current schemas and leverage these python packages for the Pydantic models.

@korikuzma korikuzma added enhancement New feature or request priority:high High priority labels Jul 16, 2024
@korikuzma korikuzma self-assigned this Jul 16, 2024
@korikuzma
Copy link
Member Author

Will also update VRS-Python version

@korikuzma korikuzma linked a pull request Nov 14, 2024 that will close this issue
korikuzma added a commit that referenced this issue Nov 20, 2024
close #388 , #395, #309

* Breaking changes
  * Update/add ga4gh packages
    * Add `ga4gh.cat_vrs` + `ga4gh.va_spec` packages 
* The Pydantic models in these packages replace the manually created
models in `metakb/schemas/annotation.py`,
`metakb/schemas/categorical_variation.py`, and
`metakb/schemas/variation_statement.py`. (#388)
    * `ga4gh.vrs` version bumped
* The models in all ga4gh packages caused breaking changes (mainly
renaming) to the evidence models (such as #395)
* Represent categorical variation members and constraints properly
(#309)
  * Standardize representing normalizer data in extensions
* The `extension.name` will always be `vicc_normalizer_data` and value
will contain `id`, `label`, and optional `mondo_id` (for disease)
* Simplify assertion checks in tests
Copy link

Closed by #404.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority:high High priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant