Auto generate models

[netpok]

This pull request allows generating model helpers automatically after migrations executed.

Basically a newer version of #842, started from the current master branch.

Based on the comment by barryvdh the config option is simplified it is named post_migrate and it is either false to disable this feature or sets the parameters for the "ide-helper:model" command. It supports both "--nowrite" and the ["--nowrite" => true] format.

The trigger was updated to use the MigrationsEnded event because Laravel will run "incomplete" commands like migrate:roll as migrate:rollback.

The other helper file generation was dropped in favor of composer post update commands.

[mfn]

Generally LGTM, I've a question (inline) though, thanks

[mfn]

LGTM!

[netpok]

I came across a project which uses the spatie/laravel-multitenancy package, thus running the basic artisan ide-helper:generate does not suffice.

Solutions in my mind:

1. Relaxing the constraint by requiring the full command to be entered, e.g: 'tenants:artisan "ide-helper:models -N" --tenant=1' would run php artisan tenants:artisan "ide-helper:models -N" --tenant=1 and maybe even allowing multiple commands e.g:['artisan command 1', 'artisan command 2', ...]. This solution would mean dropping array parameter compatibility, but I don't see that would be used too much.
2. Allowing to use a custom action, e.g.: allowing to set a callback which defaults to the current implementation GenerateModelHelper::generateWith(callback); in AppServiceProvider
3. This is an edge case which the user should handle on it's own, e.g: by overriding the generator listener, which should be possible with the current code by using $app->register(GenerateModelHelper::class, CustomImplementation::class);

[mfn]

This solution would mean dropping array parameter compatibility, but I don't see that would be used too much.

At least I can say I agree to that assertion :)

I think I would say, the bottom line for all of this would be improved DX for users of this library. Seems only 1) really fulfills this, once you "have to code" I think it gets worse. Also creates more dependencies on the internal code, which we might rather change one day…

[netpok]

I pushed a commit which implements option 1.

[mfn]

One last comment, otherwise LGTM!

[mfn]

Thanks for the other change and the clarification! I think for consistency, we also should default to [] here now:

Suggested change

	if ($this->app['config']->get('ide-helper.post_migrate', false)) {
	if ($this->app['config']->get('ide-helper.post_migrate', [])) {

[netpok]

I thought leaving this as false since its a condition but ok, changed it.

Oh, I could have just accepted the change here...

[mfn]

@barryvdh IMHO good to merge!