-
-
Notifications
You must be signed in to change notification settings - Fork 389
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
Migrations configuration key "name" does not exist. #1024
Comments
According to this issue, which is related to this issue but not the same (upgrading vs main documentation), this is indeed a documentation error. |
Looks like the name wasn't removed from Migrations while the DoctrineMigrationsBundle had this config key removed. Nice catch. Do you like to contribute a pull request for this? |
Sure, I left it just above. Thank you for inviting me to contribute! |
This has been fixed in b960657 It will be merged to master soon |
I don't agree, the commit you mention fixes the |
Bug Report
Summary
Following the documentation, I used the following
migrations.php
file:However when running
./vendor/bin/doctrine-migrations generate
as indicated on the next page, I end up with the following error :Current behavior
The error shown above
How to reproduce
Just
composer require 'doctrine/migrations'
in some empty folder, put the migrations.php file as above, and run the command above.Expected behavior
New migration class should be generated
This is fixed by commenting out the
'name' => 'Test Migrations',
line. I guess this is just a documentation error and name is not relevant anymore, but I am completely new to doctrine migrations so I can't be sure at all.The text was updated successfully, but these errors were encountered: