[5.4] Add more information to migrations #18220
Conversation
|
Do I need to fix the styles? I thought StyleCI dealt with it after the merge was committed. |
|
@gsaqui Yes, you do :) |
|
Dont really see the need with migrations but with seeders it could be nice :) |
| @@ -64,17 +64,12 @@ public function fire() | |||
| // Next, we will check to see if a path option has been defined. If it has | |||
| // we will use the path relative to the root of this installation folder | |||
| // so that migrations may be run for any path within the applications. | |||
|
|
|||
There was a problem hiding this comment.
IMO this line should be removed...
|
No plans to add this for now. |
|
@taylorotwell not really sure where the break down of communication happened. I raised this issue laravel/ideas#436 and then asked if this was something that would be accepted on https://larachat.slack.com/messages/internals and assumed that this was something that the community wanted. Where did I go wrong so next time this doesn't happen? @stefanoruth the reason I wrote this was because I have long running migrations and I'm never sure which one is running at the time and wanted the framework to give me some indication. The current situation is you don't know what is happening until the end when you get an output of the migrations that ran. |
When running a number of migrations it will give information on which migration is currently running and when the migration is finished it will say how many seconds it took to run. laravel/ideas#436