Thanks for nice tutorial ... I have doubt, why we need to use macros ? Simply create helper functions file under the app directory then load it by composer.json. kindly explain about this .. thanks again..
For most cases, they both would technically do the same thing. There are several disadvantages to importing an external functions file. First of, Laravel has deprecated helpers functions in a move to keeping everything in classes. Here's a post outlining this move laravel-news.com/laravel-5-8-deprecates-string-and-array-helpers the thought behind that is to avoid duplication. And what that means is that functions can not be namespaced the way classes are, so let's say you add a helper function file to your project with a function by the name of happy_string() and then require a composer package that also declares a function by the name of happy_string(). That package function now conflicts with yours and will yield unexpected results. The second advantage you get with a macro is the fact that is integrates with the existing Laravel classes, for example, every Eloquent query returns a Collection object with the results. You can add macros to the Collection class and now those custom functions would be available to you just as if it had shipped with Laravel. Hope that sheds some light.
Awesome videos man! I'm glad I found your channel, I'm learning new stuff that I know I will use in the future. Your video about the view composers helped a lot and together with this, I can make things so much easier than before :D Pure gold! Subscribed + bell!
The trait is actually super simple but also super useful. I'm sure laravel didn't invent this but makes me even more sure that laravel will be the next thing I want to learn.
Excellent, something laravell documentation is not exact you make it more clear and fast to understand, learning with code is the best option, i feel laravel how Ruby On Rails brother, it has a lot of thing as ROR
Another top video. I am so hungry for each of the videos in this series. I learn so much in each. I can't wait for the next one. I only discovered you in this series. Can't wait to go through the backlog.
Man, can you please announce the list of topics which we can expect being explained from you during this course? Just to wonder how far are you going to push things.
hello sir, please help me understand is there any difference between injecting service directly to function and to constructor, like class UserController extends BaseController { public $userRepository; public function __constructor(UserRepository $userRepository){ $this->userRepository = $userRepository; } public function getUsers(UserRepository $userRepository){ // 1 $this->userRepository->getAll(); // 2 $userRepository->getAll(); } }
Technically they will both work but you’re going to have to inject it into every single method in your controller. That creates unnecessary repetition. And lastly, because you don’t global access to it, if you needed a helper function, you would need to pass it the repository. All and all, you lose a lot by doing it in every single method. I would stick to the construct.
@@CodersTape thanks a lot, but one more doubt, let say i have 5 methods and each method has its own repository requirement, now if i initiate that 5 repositories into constructor, and try to call any specific method, will it try to load all repository into constructor as soon as class initialised ??
Initially I misunderstood your question. To answer it, all of them can be injected in the constructor and the instantiation cost would be extremely minimal. I wouldn’t worry about that. Remember that it doesn’t perform any queries unless you actually us it.
Question that came to mind when you reached the __callStatic method in the video...forgive me if someone already asked..I read about 30 comments and didnt see it yet.. What happens if multiple __callStatic methods exist on a class thats using a couple traits that have a __callStatic method? Im pretty sure that if the class has its own __callStatic, this will be called first and...overwrite the others?...Or not overwrite, just come first in a sequence of __callStatic calls? Not sure how to reason about it all. I do know that Laravel uses these magic methods a lot though, so I'm assuming whatever the answer is here...it can be applied to all magic method calls? (or i could be wrong again) Thanks for the great videos buddy.
@@CodersTape Ok, so what if theres two traits on a class that both have a __callStatic (and no callStatic on the class itself)? How would this play out?
You are opening my eyes on Laravel: I used not to love it too much, being forced to use it, but your videos are so great they made me want to develop like a crazy using it! :D
Hello, master wizard of laravel, Thank you very much for your excellent tutorials, I have a question, it's about real-time notifications, so that as soon as there is an event that occurs in the application such as registering a new user, that the administrator who is connected receives a real-time notification without refreshing his page, much like those of youtube, how to set up such a system (the application is installed on a server that does not have Internet access). Thank you.
@@CodersTape that's what I guessed and I upgraded the project i'm currently working on but i didn't get the pretty error page so i asked. maybe i should create a new project.
Great video! Do you have any suggestions on how to to get autocomplete to work with macros? For Models and Facades I use github.com/barryvdh/laravel-ide-helper
Thanks for nice tutorial ... I have doubt, why we need to use macros ? Simply create helper functions file under the app directory then load it by composer.json. kindly explain about this .. thanks again..
For most cases, they both would technically do the same thing. There are several disadvantages to importing an external functions file.
First of, Laravel has deprecated helpers functions in a move to keeping everything in classes. Here's a post outlining this move laravel-news.com/laravel-5-8-deprecates-string-and-array-helpers the thought behind that is to avoid duplication. And what that means is that functions can not be namespaced the way classes are, so let's say you add a helper function file to your project with a function by the name of happy_string() and then require a composer package that also declares a function by the name of happy_string(). That package function now conflicts with yours and will yield unexpected results.
The second advantage you get with a macro is the fact that is integrates with the existing Laravel classes, for example, every Eloquent query returns a Collection object with the results. You can add macros to the Collection class and now those custom functions would be available to you just as if it had shipped with Laravel.
Hope that sheds some light.
@@CodersTape Many thanks ..now I have clear view ... Keep rock ..we are looking more interesting videos
@@CodersTape i read it like you are speaking it.. heeh
I'll go ahead and leave a like before even watching cause i knw it's gonna be GOLD
first time i watch a video on youtube that has no dislikes that means this great instructor going to take place of traversy media
I couldn't get enough of the macros after watching this.
Awesome videos man! I'm glad I found your channel, I'm learning new stuff that I know I will use in the future. Your video about the view composers helped a lot and together with this, I can make things so much easier than before :D Pure gold! Subscribed + bell!
Thanks for watching.
Good job brother.
Can u make a video in lazy colletion vs collection.
Thank you l love it .
Very nice tutorial please when will Laravel 7 or 8 advance tutorial be available. Thank you
Thanks for the video! Keep up the great work!
Good job my friend, i'm learning so so much with this lessons. Thanks a lot!!!
The trait is actually super simple but also super useful. I'm sure laravel didn't invent this but makes me even more sure that laravel will be the next thing I want to learn.
*There doesnt look to be too many new features in 𝐋𝐀𝐑𝐀𝐕𝐄𝐋 6*
Not at all. It’s a maintenance update and just a lock down of the framework structure
Thanks Man.. you're awesome!
Thank you awesome explanation
Hi, Can you upload your codes to access them?
please make a accounting web site for example & live practice
Hey bro if u got tuts please share
Excellent, something laravell documentation is not exact you make it more clear and fast to understand, learning with code is the best option, i feel laravel how Ruby On Rails brother, it has a lot of thing as ROR
Incredible feature
Another top video. I am so hungry for each of the videos in this series. I learn so much in each. I can't wait for the next one. I only discovered you in this series. Can't wait to go through the backlog.
Man, can you please announce the list of topics which we can expect being explained from you during this course? Just to wonder how far are you going to push things.
That boot method inside the AppServiceProvider looks like a dumpster to me
I'm just a simple web developer. My phone notified me for new Coder's Tape video. I watch it.
Thanks!
Thanks!
Welcome back
this is awesome! Thanks for your super clear tutorials. Keep up the good work man.
new thing to me
thanks alot for tutorial ... it is the best playlist i have ever watch .
I really love your teaching methods and your knowledge, thanks mate :)
Make:auth not defined in laravel 6? plzz help me sir
laravel-news.com/running-make-auth-in-laravel-6
@@CodersTape Thankyou so much sir it's work
hello sir, please help me understand is there any difference between injecting service directly to function and to constructor, like
class UserController extends BaseController {
public $userRepository;
public function __constructor(UserRepository $userRepository){
$this->userRepository = $userRepository;
}
public function getUsers(UserRepository $userRepository){
// 1
$this->userRepository->getAll();
// 2
$userRepository->getAll();
}
}
Technically they will both work but you’re going to have to inject it into every single method in your controller. That creates unnecessary repetition. And lastly, because you don’t global access to it, if you needed a helper function, you would need to pass it the repository. All and all, you lose a lot by doing it in every single method. I would stick to the construct.
@@CodersTape thanks a lot, but one more doubt, let say i have 5 methods and each method has its own repository requirement, now if i initiate that 5 repositories into constructor,
and try to call any specific method, will it try to load all repository into constructor as soon as class initialised ??
Initially I misunderstood your question. To answer it, all of them can be injected in the constructor and the instantiation cost would be extremely minimal. I wouldn’t worry about that. Remember that it doesn’t perform any queries unless you actually us it.
@@CodersTape Great, Thanks, Also Joined coderstape.com
I knew it! Thanks Man.. you're really awesome!
#Coder's Tape , Please Explain mircoservices with Laravel
As an extraction?
@@CodersTape yes, and laravel modulartiy
In one world sir, You are awesome
Thanks
Please do a video on service providers
It's more than clear thanks a lot
great! wanted more from you
Question that came to mind when you reached the __callStatic method in the video...forgive me if someone already asked..I read about 30 comments and didnt see it yet..
What happens if multiple __callStatic methods exist on a class thats using a couple traits that have a __callStatic method? Im pretty sure that if the class has its own __callStatic, this will be called first and...overwrite the others?...Or not overwrite, just come first in a sequence of __callStatic calls? Not sure how to reason about it all. I do know that Laravel uses these magic methods a lot though, so I'm assuming whatever the answer is here...it can be applied to all magic method calls? (or i could be wrong again)
Thanks for the great videos buddy.
You’re correct. They will get overwritten by the class static and ignore all traits.
@@CodersTape Ok, so what if theres two traits on a class that both have a __callStatic (and no callStatic on the class itself)?
How would this play out?
You are opening my eyes on Laravel: I used not to love it too much, being forced to use it, but your videos are so great they made me want to develop like a crazy using it! :D
Glad to hear! Good job sticking with it.
Glad to hear! Good job sticking with it.
The BEST as always!
Hello, master wizard of laravel,
Thank you very much for your excellent tutorials, I have a question, it's about real-time notifications, so that as soon as there is an event that occurs in the application such as registering a new user, that the administrator who is connected receives a real-time notification without refreshing his page, much like those of youtube, how to set up such a system (the application is installed on a server that does not have Internet access).
Thank you.
Without internet you wouldn’t be able to send out the notification. You can use Laravel Echo, we have not covered it yet but we will.
@@CodersTape But what about laravel sockets?
Dieudonné NIEME sockets will still require internet connection
@@CodersTape Try to have a look on this docs.beyondco.de/laravel-websockets/
@@CodersTape Try to have a look on this docs.beyondco.de/laravel-websockets/
Boom!
I should put that on a tshirt or mug
@@CodersTape Definitely :))
very helpfull, thank you sir.
8:26 how is your error page so pretty?
Laravel 6
@@CodersTape that's what I guessed and I upgraded the project i'm currently working on but i didn't get the pretty error page so i asked. maybe i should create a new project.
composer require facade/ignition
Great video! Do you have any suggestions on how to to get autocomplete to work with macros?
For Models and Facades I use github.com/barryvdh/laravel-ide-helper