Route::controller() in Laravel 5.3

From my understanding, Route::controller() was phased out of the docs in version 5.1 implying they scheduled it to be deprecated in a future version, in this case 5.3.

Route::controller() was replaced with Route::resource() which sends the request to the correct controller action based upon the type of http request. It is closest option to replace Route::controller() with. Unfortunately, there will have to be refactoring in your controllers if you decide to migrate to 5.3

@codersrini I guess there is, however I suggest you just create those explicit routes. Here's something that can help you out https://gist.github.com/jarektkaczyk/09c2540564ccbe31b2540a03687125b0

Thanks guys. Let me tryout both the suggestions. Thanks again for the quick responses.

Why on earth did they remove this function? I really like the fact that I can see in the controller which method belongs to which URL. Currently I'm working on a project with hundreds of routes and like 40 controllers and it's a complete chaos when I need to put them all in the routes file(s). All my URL's are build like this:

products -> getIndex()
products/new -> getNew()
products/new -> postNew()
products/edit/{product_id} -> getEdit($product_id)
products/edit/{product_id} -> postEdit($product_id)
products/delete/{product_id} -> postDelete($product_id)

Is it possible to build a package so I will be able to keep working with the Route::controller() method?

@Vinze Have you looked at Resource Controllers - https://laravel.com/docs/5.3/controllers#resource-controllers

They seem to do exactly what you are doing?

@tonym When using resource controller I need to use the exact methods names and routes as defined in the documentation. I also have functions like getImport, postImport, getExport and so on, which means I have to manually create this routes because they are not CRUD.

Ah ok. In that case you will have to explicitly create those routes.

Have a look at this as to why it was removed - https://laracasts.com/discuss/channels/laravel/why-is-routecontroller-deprecated

This is also an interesting read on a way to structure your controllers - http://jeromedalbert.com/how-dhh-organizes-his-rails-controllers/

@Vinze just follow the REST convention and your done (shortcut with route:resource())

Unfortunately I can't follow the REST convention because the routes are predefined by some other software which pulls data from my application. It has been removed is because they say it's explicit. I don't share that opinion, and because I can't use the REST convention I'm forced to fill my routes file with hundreds of entries instead of mapping the routes to 40 controllers. Wheres the clarity in that?

Maybe I can hack it back into the framework, but that's not the way I like to solve this problem. Would it be possible to write a service provider or something like that to restore the Route::controller function?

Hi @codersrini , that can help you https://github.com/themsaid/laravel-routes-publisher

Here is the add-back code, easy implementation:

https://github.com/shrimpwagon/laravel-route-controller