Remove schema shell from 3.0 #2146
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
Remove the schema shell. I don't think we are going to have time to build a proper replacement for 3.0.0. I also think that migrations are something that would be better handled in a plugin where ideas can be iterated more quickly and compatibility constraints are less strict.
|
👍 |
|
Agree 👍 |
|
Totally agree (as I already said in general in my Google Groups post)! |
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.
Remove the schema shell. I don't think we are going to have time to build a proper replacement for 3.0.0. I also think that migrations are something that would be better handled in a plugin where ideas can be iterated more quickly and compatibility constraints are less strict.
Once the main development push for 3.0 settles down I'd like to properly revisit migrations and possibly extend/enhance existing solutions like cakedc/migrations instead of building yet another migrations tool.