Skip to content
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

Better reversible migrations #1164

Merged
merged 3 commits into from
Sep 7, 2017
Merged

Better reversible migrations #1164

merged 3 commits into from
Sep 7, 2017

Conversation

Roy-Orbison
Copy link
Contributor

Enables otherwise irreversible migrations to become reversible, and makes
it possible to use a single migration where previously two were required.

Pursuant to #1151

Enables otherwise irreversible migrations to become reversible, and makes
it possible to use a single migration where previously two were required.
@@ -66,6 +66,11 @@
protected $input;

/**
* @var bool
*/
protected $goingUp;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would not be a boolean or be accurate when using the up and down methods, would it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@Roy-Orbison
Copy link
Contributor Author

Roy-Orbison commented Sep 3, 2017 via email

@lorenzo
Copy link
Member

lorenzo commented Sep 4, 2017

It does seem superfluous, but it is not. Having the state of an object consistent is important because you don't know the different permutations a particular object can be used

@mvrhov
Copy link
Contributor

mvrhov commented Sep 5, 2017

So should I close the #788 ?

@lorenzo
Copy link
Member

lorenzo commented Sep 7, 2017

@mvrhov yes

@lorenzo
Copy link
Member

lorenzo commented Sep 7, 2017

Thanks!

@lorenzo lorenzo merged commit 3d39d9d into cakephp:master Sep 7, 2017
@mvrhov
Copy link
Contributor

mvrhov commented Sep 7, 2017

@lorenzo I know you already merged but? Wouldn't it be better if getGoingUp would be named isMigratingUp and the set method setMigratingUp

@lorenzo
Copy link
Member

lorenzo commented Sep 7, 2017

@mvrhov Sure, it like that.. care to open a new PR with the change?

@mvrhov
Copy link
Contributor

mvrhov commented Sep 8, 2017

Sorry I don't have time :/ Maybe @Roy-Orbison can find some.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants