Store history of level metadata - #879
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #618.
This is the primary reason I implemented migration jobs - after startup Refresh will automatically begin populating the
GameLevelRevisionswith the current state of GameLevels.I also removed
Write(Action)calls in favor ofSaveChangesin a couple places I touched - this makes the diff a bit messy but I only changed that and added a call to create the revisions. Should be easy to review still. I made some minor adjustments to theMigrationJobclass to add logging and enforce ordering to be implemented.This PR doesn't handle retrieval through any APIs - that will be handled in a follow-up PR. This PR only concerns storage.