Generalize migration process #283
Merged
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
License: MIT Signed-off-by: Wyatt Daviau <wdaviau@cs.stanford.edu>
ghost
assigned 
|
Changes Unknown when pulling 652ba56 on feat/migration-framework into ** on master**. |
Will improve as we need it I guess... Thanks! |
Closed
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This is meant to address issue #230. It implements the ideas put forward there to help ease the development of state migration changes when format versions increase. With so few supported versions at present the overhead may seem unnecessary but it should start obviously paying off when we get to version ~10.
@hsanjuan there is still a lot of updating required in the case of a version increase. Suggestions to improve this are particularly welcome.