-
Notifications
You must be signed in to change notification settings - Fork 28
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(migration): enable automatic data migrations between versions #245
base: release-0.3.0
Are you sure you want to change the base?
feat(migration): enable automatic data migrations between versions #245
Conversation
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 think I'll leave the Talent Tree sign-off to @stanavdb, though to me it looks about right.
But one other point (plus my comment on the character migration script): Do we want to add a method to call this manually from somewhere? may not be one for implementing this ticket, but food for thought...
// ), | ||
// ); | ||
// } | ||
|
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.
Also needs a level value change, previously it was typed as string I think? but now that the advancement is in it's a number.
Can see examples of this with the B9 pregens
Type
What type of pull request is this? (e.g., Bug fix, Feature, Refactor, etc.)
Description
This PR establishes an automatic method for performing data migrations, for cases where breaking changes are introduced to the model between versions. It automatically checks for all migrations between the last known system version in the given world and the new version of the system, and attempts to convert the previous data to the known schema from that version.
To-Do List
Related Issue
Closes #244
How Has This Been Tested?
Checklist:
Additional Context:
The bulk of this PR is based on Stan's blueprint. It has largely been updated to be type-safe and functional with the latest changes to the data model, especially following the changes to talent trees.