Conversation
|
VRS 2.0.0-ballot.2024-11.3 will be made later tonight. Will update submodules afterwards |
jsstevenson
left a comment
There was a problem hiding this comment.
2 small requested changes (typos) and a few recommendations
| path = submodules/vrs | ||
| url = https://github.com/ga4gh/vrs.git | ||
| branch = 2.x | ||
| branch = 2.0.0-ballot.2024-11 |
There was a problem hiding this comment.
is there a reason why we're pinning a branch and not a tag? I'd think we would want to be pinning specific commits. Submodules always hurt my brain though so maybe I'm misunderstanding.
(ditto for VRS -> gks-core, outside scope of this PR though obviously)
There was a problem hiding this comment.
I might have missed something when googling before but tags aren't supported in .gitmodules so I opted for the branch
There was a problem hiding this comment.
maybe we can punt this to an issue but I think commit would be appropriate (and it's effectively the same as a tag name). Otherwise there's a risk that changes to the submodule'd branch run ahead of what's expected in the superproject.
close #469
_Ga4ghIdentifiableObjecttoGa4ghIdentifiableObjectentity_modelsanddomain_modelsfromga4gh.core. Now, all gks-core models are inga4gh.core.models.dateanddatetimeas primitives, however the builtindatetimemodule already provides these. Initially, I kept them as Pydantic Root Models but I think we should just leverage thedatetimemodule instead.