Error on using reserved keyword for migration name#2328
Merged
MasterOdin merged 3 commits into0.xfrom Dec 2, 2024
Merged
Conversation
Co-authored-by: Mark Scherer <dereuromark@users.noreply.github.com> Signed-off-by: Matthew Peveler <matt.peveler@gmail.com>
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 #2326
PR makes it so that if using a reserved PHP keyword for a migration name, an error will now be raised for that command. Previously it would allow the migration to be created, but then fatal error on trying to parse that migration.
This is a port of cakephp/migrations#780, though I opted out of asking the user a question as part of the flow and just have it error out altogether for simplicity sake.