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

feat!: update vrs 2.0-alpha models #257

Merged
merged 8 commits into from
Sep 12, 2023
Merged

feat!: update vrs 2.0-alpha models #257

merged 8 commits into from
Sep 12, 2023

Conversation

korikuzma
Copy link
Contributor

Notes:

  • Made use of the classes in core-source/vrs-source so we don't repeat code
  • Tried to reorganize some models
  • Changed enums keys to uppercase
  • For ga4gh_identify/ga4gh_serialize/ga4gh_digest, let me know if there's a cleaner way to handle SequenceReference
  • Update tests since digests changed

@korikuzma korikuzma added 2.0-alpha Issues related to VRS 2.0-alpha branch priority:high High priority labels Sep 11, 2023
@korikuzma korikuzma self-assigned this Sep 11, 2023
@korikuzma korikuzma requested review from a team as code owners September 11, 2023 21:47
@korikuzma korikuzma removed request for a team September 11, 2023 21:47
@@ -329,8 +498,7 @@ class SequenceLocation(BaseModel):
description='The end coordinate or range of the SequenceLocation. The minimum value of this coordinate or range is 0. MUST represent a coordinate or range greater than the value of `start`.',
)

class ga4gh:
identifiable = True
class ga4gh(_Ga4ghIdentifiableObject.ga4gh):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Originally I put these properties in a nested class in order for them to not be seen as related to the top level pydantic properties but still be declared on and accessible on the class. This change seems fine to share some of the structure of the .ga4gh nested classes, but if we can think of a cleaner way that'd also be nice.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmmm @toneillbroad do you have any suggestions? If not, we can make a separate issue for this and come back to it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The structures as represented in this PR are good by me.

@korikuzma korikuzma merged commit f8ed3b1 into 2-alpha Sep 12, 2023
0 of 8 checks passed
@korikuzma korikuzma deleted the issue-256 branch September 12, 2023 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.0-alpha Issues related to VRS 2.0-alpha branch priority:high High priority
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants