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');
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 ?
Personally I'm a fan of Laravel and recommend it to anyone but it depends on your preference, again. It's like choosing which car to drive or which phone to buy.
Depends on the friend's reasoning. It is a fantastic platform to create an app from, there are some fantastic resources for learning Laravel, it has 3 different solutions for having Users log into the App, from very simple to very comprehensive.. It may be overkill for some websites, but jesh is it a fantastic platform to create a meaningful Website. Butttt, it may not be the best choice for some Websites/Apps. All depends on what you need and want to do. There are some mighty big companies that use Laravel, which may lead some people to think that it is not a stupid thing to learn. :-)
@@ahmadkhaled7497 Go to do this approach when you applying for the company. I bet you get rejected. Also serious single responsibility principle violation. Controller should never ever contain private method
Your statement is not flexible, please stop blaming culture. Counterargument to your situation: if you're already working at a company and your task is to quickly launch this project and you deliver in 2 hours instead of 8 hours with all design patterns, you may get PROMOTED. It all DEPENDS.
@@LaravelDaily I have several coding tasks for companies where code works fine. But I was rejected for doing something like this. But with tight deadline it's approvable with room to improve.
really like this code reviews!
These code reviews are really great!
Out of 2.6K views, only 145 of us could rate this ? Jeshhhhhhh.
Personally, I prefer to use resources instead of single get or post route because you easily extend routes in future with minimal work around.
Please create a video about Manticore Search, is it better than Melisearch and elasticsearch? Should we use this in our projects? Thanks
Haven't tried it. I personally use Algolia.
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');
Yes if you're querying it ONLY in routes. Model key allows you to call Model::find($slug) from anywhere
Would it be advisable to group the routes using the same middleware ? And then within that group, create another group for the controller ?
Yes that's another option. It's your personal preference, generally.
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 ?
It's a personal preference depending on which projects you work on
@@LaravelDaily if its eucational site videos courses exams questions and answers ?
Personally I'm a fan of Laravel and recommend it to anyone but it depends on your preference, again.
It's like choosing which car to drive or which phone to buy.
@@LaravelDaily thank you
Depends on the friend's reasoning. It is a fantastic platform to create an app from, there are some fantastic resources for learning Laravel, it has 3 different solutions for having Users log into the App, from very simple to very comprehensive.. It may be overkill for some websites, but jesh is it a fantastic platform to create a meaningful Website.
Butttt, it may not be the best choice for some Websites/Apps. All depends on what you need and want to do. There are some mighty big companies that use Laravel, which may lead some people to think that it is not a stupid thing to learn. :-)
Very juniorish code.
It's a simple project, no need to make things complicated.
@@ahmadkhaled7497 Go to do this approach when you applying for the company. I bet you get rejected. Also serious single responsibility principle violation. Controller should never ever contain private method
Your statement is not flexible, please stop blaming culture. Counterargument to your situation: if you're already working at a company and your task is to quickly launch this project and you deliver in 2 hours instead of 8 hours with all design patterns, you may get PROMOTED.
It all DEPENDS.
@@LaravelDaily I have several coding tasks for companies where code works fine. But I was rejected for doing something like this. But with tight deadline it's approvable with room to improve.
@@bumblebity2902 "Controller should never ever contain private method". Why not?