[5.3] Create a resource controller along with the model

[browner12]

it's incredibly common for me to make a resource controller for most of my models, so it'd be nice do it in one line.

while this would be a nicety, I can also see someone arguing that this adds unnecessary complexity, when it's already easy enough to just run the commands one after the other.

curious where you stand on this, because we could just as easily add an option to create a seeder at the same time.

[taylorotwell]

One question for me here would be what if I want the controller in a namespace, like API for example?

[browner12]

i think when you're adding a nicety like this, you really can't cover all use cases, and what you're going after is a majority. trying to cover everything causes you to add in little hacks that turn the once simple change into messy code.

I would say keep the feature and code simple, and for more complex things (ie namespaced controllers), you can continue to use the dedicated commands.

for me, personally, most of my controllers are never in a namespace, so this covers 99% of my use. maybe it's different for others, would be curious to hear.

[Modelizer]

It's very rare I use a controller without adding namespace. I was thinking can we add Controller Namespace? --cn=YourNamespace option?

Or else we can swap it out like

php artisan make:controller Namespace\ControllerName --model

Here most of the time I put controllers into namespace but keeping Model in its default directory

---

Also, I was thinking can we set model default directory in a configuration file? This way we can control model not to always create in App directory.