The "tell, don't ask" example is more about two things: declarative programming; and a bit about separating the domain of the code - instead of creating some extended logic in the code, that is not the domain of the lessons (let's say a code for singing in, more about the participant, than the lesson itself), I prefer to create logic of the lesson in the lesson class/domain, and allow other domains to have minimal contact with this logic. Thanks to that when debugging such a code - you won't be surprised by an "alien" code.
Wow, that is a great share. Hi chief, I would suggest you make a video related to event-sourcing in Laravel. What are the real-world use cases? A simple explanation that everyone can understand.
Hello Povilas, would have a tip for a redirect with string data? Within a method I sometimes must redirect to another route, with a string value as parameter. The documentation says do this: return redirect()->route('profile', ['id' => 1]); and it works perfectly. Except that my parameter is a string and the URL looks ulgly because the paramater gets passed as a GET. Is there a fix for that?
You must pass HTTP code parameter 307 - Temporary Redirect - to the redirect method. With 307 code you are able to redirect POST request. Please let me know if it helped you. Thanks.
@@LaravelDaily Ohh excuse me, I am so bad with these terms. I was actually thinking about eager loading but didn't realize that lazy loading is different. Thank you!
Yes! Please continue with monthly tips!
Very good and efficient tips.
Please continue this.
This is a DARN GOOD tradition, thank you!
i love this tips make me learn new things, most likely i will forget them again but i know where to come when need remember something
The "tell, don't ask" example is more about two things: declarative programming; and a bit about separating the domain of the code - instead of creating some extended logic in the code, that is not the domain of the lessons (let's say a code for singing in, more about the participant, than the lesson itself), I prefer to create logic of the lesson in the lesson class/domain, and allow other domains to have minimal contact with this logic. Thanks to that when debugging such a code - you won't be surprised by an "alien" code.
Great work sir 👍, please continue
Yes Please. You are doing great work man❤
amazing keep going! 🙏🏻
1:32 Before using to_route(), I usually confuse (how to redirect with route) without looking documentation
Wow, that is a great share. Hi chief, I would suggest you make a video related to event-sourcing in Laravel. What are the real-world use cases? A simple explanation that everyone can understand.
I haven't used it myself, so can't explain to others :)
These were great tips!
This is helpful, thank you.
Hello Povilas, would have a tip for a redirect with string data?
Within a method I sometimes must redirect to another route, with a string value as parameter.
The documentation says do this:
return redirect()->route('profile', ['id' => 1]);
and it works perfectly. Except that my parameter is a string and the URL looks ulgly because the paramater gets passed as a GET.
Is there a fix for that?
Not sure, maybe you defined the route the wrong way? I haven't encountered this issue.
@@LaravelDaily Please try the eample from the book, but with a string parameter (a sentence). As I said, evrything works fine but the URL is ugly.
Sorry, I don't have time to try, could you post the code of your profile route from the routes file?
You must pass HTTP code parameter 307 - Temporary Redirect - to the redirect method.
With 307 code you are able to redirect POST request.
Please let me know if it helped you. Thanks.
Thanks for the tips!
Awesome these are nice to know
Thanks for re-posting passing variables to a View
Tip: "Don't use Rails"
Another thing is making utilities instead of helpers. Game changer 😮
What's the difference?
2:03 is this only obvious for those that have done a lot of PHP before doing Laravel?
What's the point of disabling lazy loading? I though Laravel guys recommend it.
Enforcing EAGER loading, to avoid N+1 query problem.
@@LaravelDaily Ohh excuse me, I am so bad with these terms. I was actually thinking about eager loading but didn't realize that lazy loading is different. Thank you!