#94 Add support for upgrading DeverJson & DotDever when schema has been modified #219
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
…and instead using the config-facade.js + Added support for migrating .dever
+ Minor improvements for execution of migrations
… be modified through the config section
czprz
deleted the
94-add-support-for-upgrading-dever-jsondot-dever-when-schema-has-been-modified
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Describe your changes
Added migration like logic for handling changes and updates to dever configuration files, making it easier going from older versions
Issue ticket number and link
#94 Add support for upgrading dever-json/dot-dever when schema has been modified
Checklist before requesting a review
Closes #94