[5.0] Adds "--path" to the migrate:reset command

[chrisbjr]

Hi all,

I've added a --path option to the migrate:reset command.

Usage for this should be similar to the php artisan migrate --path="..." command.

So after doing the above command, you can do this:

php artisan migrate:reset --path="..."

I'm adding this because we have the option of doing a migration from a specified path but have no option to reset the migration from that path itself.

Hoping you consider this pull request.

Thanks
Chris

[Marwelln]

This indentation seems to be wrong.

[RomainLanz]

You change files permissions. Care about that.

[chrisbjr]

@RomainLanz i missed some of those - just figured out that laravel doesn't follow PSR-2 coding style. Thanks for pointing those out.

[RomainLanz]

Laravel doesn't follow PSR-2 now, probably on the future.

Still dot missing on line 182.

[GrahamCampbell]

Please squash to one commit.

[chrisbjr]

Hi @GrahamCampbell done. Thanks!

[GrahamCampbell]

You should maybe just use glob in the first place?

[chrisbjr]

@GrahamCampbell now using glob instead of scandir. Glob returns the full path of the files though but using basename did the trick. It even has a handy suffix parameter that can be used to remove the file extension.

Let me know if you're ok with it and I can squash to one commit again.

[GrahamCampbell]

missing a new line before this block.

[chrisbjr]

@GrahamCampbell moved

[GrahamCampbell]

Thanks.

[taylorotwell]

I'm not sure why this would be needed? migrate:reset should roll back all migrations.

[chrisbjr]

Hi Taylor

Here is an example use case:

Let's say I wanted to install a Laravel package and it has its own migration files. Part of the instructions would be to migrate them using php artisan migrate --path="...".

But let's say we don't need the package anymore and wanted to remove only the migrations from that package without having to touch the main application's tables. Or another scenario would be that there was an updated migration file from the package. We don't want to reset the whole database just for this package.

In this case, we can use php artisan migrate:reset --path="..." and not touch the main tables. It makes sense to enable resetting from the path if we can migrate from a path.

[pilot911]

good idea, also why we have only one hardcoded in config emailView for reset password ?
think those problems from one way - you Tailor should think wider about modularity

[taylorotwell]

Going to hold off on this for now.

[clrke]

+1 great feature but please redo it for 5.1

[coveralls]

Changes Unknown when pulling f7ce2d5 on chrisbjr:5.0 into * on laravel:5.0*.