'Built with Laravel' Code Review: Routes and Controllers

Start of a mini-series, reviewing the code of open-source project by Tighten called "Built with Laravel". In this video, we're talking about Routes and Controllers.

Links mentioned in the video:

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:

[handymanus]

Out of 2.6K views, only 145 of us could rate this ?

[shahsawoodshinwari]

Personally, I prefer to use resources instead of single get or post route because you easily extend routes in future with minimal work around.

[handymanus]

Would it be advisable to group the routes using the same middleware ? And then within that group, create another group for the controller ?

[AhsanKhan]

Please create a video about Manticore Search, is it better than Melisearch and elasticsearch? Should we use this in our projects? Thanks

[hodapro]

I used to use laravel to build my apps but one of my friends told me it is stupid thing to choose laravel nowadays is he wrong or right ? I am confused ? I like laravel actually but do I need to go to learn another stack ?

[virinom]

There is a simpler way to route by slug. With this way no need to add any method inside model class, and it works just file like ID based route-model binding.
Route::get('services/{services:slug}', [\App\Http\Controllers\Frontend\ServiceController::class, 'show');