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

Ability to do dry run instead of actual migration generation (cycle:migrate) #10

Open
alexndr-novikov opened this issue Feb 11, 2020 · 0 comments
Labels
help wanted Extra attention is needed type:enhancement Enhancement.

Comments

@alexndr-novikov
Copy link
Contributor

It will be useful for developers to have an ability to see changes before actual generation of migration file.

Usual workflow of development that includes schema changes now looks like this:

  1. cycle:migrate
  2. wait till file appear in host system filesystem (when using docker volume it takes 1-2 seconds to appear in file system and be indexed by phpstorm)
  3. open file, check diff.
  4. if something is missing - remove file, make entity file schema changes, go to p.1

My suggestion is to add some flag like --dry, which will not generate actual file, but just print the result to console, where you can immediately see the difference

php app.php cycle:migrate --dry
@alexndr-novikov alexndr-novikov added type:enhancement Enhancement. help wanted Extra attention is needed labels Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed type:enhancement Enhancement.
Projects
Status: Backlog
Development

No branches or pull requests

1 participant