As a dev coming Symfony, there are things that I like about Laravel and there are things I don't like. Symfony scaffolding is much less tedious since you generate the controllers and models pretty quickly. The amount of plugins for Laravel is really nice though.
24:25 When i saw that authorize method in StoreMessageRequest, it kind of reminded me of Policies. So then, what is the difference between writing auth guards in the Request vs creating a Policy for each controller method ?
Among many things to understand, the auth method in the request class expects the return type to be either true or false, depending on whatever logic you put in place. This doesn't interfere with writing policy, because using a similar policy it will be easier in that auth method to identify if the current auth->user has permission to perform that action. Second, some controller methods don't expect to have a request class, so policies here play an important role.
I use docker environment (Devilbox), whenever I use Laravel new command to install the application, it never give me options to select various settings as yours, do I need update Laravel Installer in my environment?
Hello! Thanks for the example, but I can't see validation errors as you can on 12:00. In my case, this loop code works: @foreach($errors->default->messages() as $error){{ $error[0] }}@endforeach , because $errors have a large inner structure, and not just an array of strings....
![BabyChiefDoit - Too Slow (feat. STAR BANDZ) [Official Music Video]](http://i.ytimg.com/vi/zayaxws7RPg/mqdefault.jpg)
I start to understand why Laravel is becoming so popular given such quality tutorials 👍
As a dev coming Symfony, there are things that I like about Laravel and there are things I don't like. Symfony scaffolding is much less tedious since you generate the controllers and models pretty quickly. The amount of plugins for Laravel is really nice though.
24:25 When i saw that authorize method in StoreMessageRequest, it kind of reminded me of Policies. So then, what is the difference between writing auth guards in the Request vs creating a Policy for each controller method ?
Among many things to understand, the auth method in the request class expects the return type to be either true or false, depending on whatever logic you put in place. This doesn't interfere with writing policy, because using a similar policy it will be easier in that auth method to identify if the current auth->user has permission to perform that action. Second, some controller methods don't expect to have a request class, so policies here play an important role.
❤❤ more love jefery
I use docker environment (Devilbox), whenever I use Laravel new command to install the application, it never give me options to select various settings as yours, do I need update Laravel Installer in my environment?
Insightful 💡
Respect from Pakistan 🇵🇰
What's the point of not using Stacks? I might be wrong, but as a JS/TS developer, I only came to Laravel so I can kick-start my ideas ASAP.
Hello! Thanks for the example, but I can't see validation errors as you can on 12:00. In my case, this loop code works: @foreach($errors->default->messages() as $error){{ $error[0] }}@endforeach , because $errors have a large inner structure, and not just an array of strings....
best refresher ❤
anybody knows what vs code theme he uses?
Carbon Theme (by Oscar Newman)
An amazing job
I know is a dumb question but, what browser is he using?
Arc
I would like to see more Laravel videos like this. Thank you!
First. Best channel ever
🤡
Best Channel ever