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.
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: HiFa v1.1.0 schema development #1978
base: main
Are you sure you want to change the base?
feat: HiFa v1.1.0 schema development #1978
Changes from all commits
4934ed9
2569988
bb7b416
3dd5766
81c5816
9a67f9f
c9da4e3
bc8de57
475c08e
a4358c6
8d67cc4
f30da27
a2f4899
41a0b23
58c79f0
7b60642
58fe1b7
9b8ea83
691a3b5
26a5f32
b75ab60
b15850c
b91ee76
c89eff0
8f10cd8
b6edb60
f854c23
4f84a65
06f13a9
4563ae3
3bb4d0e
fcfab82
862aabb
6249ffa
f05cb95
531e0ba
bc7fffa
e66d252
f1df51f
372c8d2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm missing something about what the purpose of
upgrader
is, but is there a reason why we need to make this class schemav1.0.1
hardcoded?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need an
Upgrade_X_Y_Z
class for every single version we plan to support upgrading to. When we add a new version of the spec, we have to have a new upgrade class that knows how to upgrade from an old version to the version the class represents.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kratsg Ah okay, so the real reason is that we can't deterministically know what version we're upgrading from in advance?
Do we have a plan for how to handle upgrading multiple versions in one go? e.g. Let's say we have
v1.0.0
,v1.1.0
,v1.2.0, and
v2.0.0. If at this point someone comes along with a
v1.0.0schema and wants to move from
v1.0.0to
v2.0.0` what's the plan for doing this?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have ideas on how to do this with python's
mro
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow up to the above.