Sometimes you see or learn something but you skim over it so quick or haven't been in a situation where you needed it, then later on you do see a use for it but forgot about it, what you did was basically just highlight the information already available so that I can go "Ahh okay now I get it". Thanks! Like sometimes you learn things you don't need to know at the start and forget about it later on, and with so much to learn you don't always think of going back to the things you already went over in the past.
On tip 10 with route to view, avoid calling à function to pass data from eloquent for instance, to the view. The function Will be called each time the backend receives à request and the route file is parsed.
so the cloning part. Is the purpose of this so that the $query variable is not changed when added modifiers are applied? How would the unverified users result be affected if the clone wasn't applied? Would this be useful if i needed to call several groups of data for instance? Lets say, when i need to filter data based on users who are male or female. Would the base query pull all users, then the sub queries separate the two without additional calls to the database? Or is that something different? I've had a few situations where i was querying the same table for different data sets and needed them to be individualized variables, and was wondering how to do so without multiple queries. Most of the times, I'd end up with a new query for each grouping, so i didnt think I was doing it right
People not reading docs is a pain Also in regards to the "clone" you should probably tell people what happens under the hood, meaning the way that memory is allocated. Cloning an object is something more advanced in the OOP section and a lot of people, either coming from bootcamps or university, don't know about. If you don't you will run in the problem that people on social media applaud you just because you sound smart In regards to validating "nullable" vs "sometimes required", nullable from what i remember requires the key to exist in the payload but can have value null, while sometimes applied a isset check
I'm not sure why/how it would be useful though. If you don't want the users to use that column, just remove it from the request. Or maybe even put it into the $guarded array.
@@kemal6039 It wasn't a question of how useful it is. But I, for example, have a few use cases for it, especially for transparency in admin panels when the form changes due to certain settings.
I'd personally love it if folks sharing Laravel tips could mention the version they're for. Makes life easier for everyone! 😄
Or, you can always upgrade to the latest version and make life easier for yourself :)
@@LaravelDaily now, you know damn well it's not feasible to alway be on the newest version within the real world corporate context
Sometimes you see or learn something but you skim over it so quick or haven't been in a situation where you needed it, then later on you do see a use for it but forgot about it, what you did was basically just highlight the information already available so that I can go "Ahh okay now I get it". Thanks!
Like sometimes you learn things you don't need to know at the start and forget about it later on, and with so much to learn you don't always think of going back to the things you already went over in the past.
thank you for this video all of these tips didn't know any of them despite being in laravel documentation 24 / 7
Thanks a lot! Great tips and several of them are new for me! We want more! :)
The PEST architectural test tip is nice..... I would be interrested to know more what PEST can do.
I have a few videos, search the channel.
And, of course, read Pest docs :)
Muy bueno!!! You have fans speaking spanish too 😀
nice, it shows how much information the documentation have that i will never find by myself 😆
there are also methods abort_if and abort_unless, which are also shorten abort conditionals
Thank you very much (from Uzbekistan, Fergana)
Nice set of tips, thank you.
Sorry for my ignorance, but, is there some way to apply the second tip (arch tests), but using PHPUNIT instead of Pest?
No, it's a pest function.
Maybe phpunit has something but I haven't heard of it.
nice!
and btw I agree it's twitter not "X"
Know most of this but still i liked this concept of teaching 😀
I use twitter, I only subscribed on youtube. Thanks for sharing.
On tip 10 with route to view, avoid calling à function to pass data from eloquent for instance, to the view. The function Will be called each time the backend receives à request and the route file is parsed.
Yes tips ones are great !
Is the MAIL_DRIVER=log example still valid in LARAVEL 11? Because the default .env does not contain a MAIL_DRIVER entry...
From what I remember, it was renamed to MAIL_MAILER or something. Now off computer to check.
@@LaravelDaily You are correct. MAIL_MAILER it is.
how beneficial (or not) is using clone for queries comparing to just working with the initial collection?
Great tips, i knew only 5 tips)
so the cloning part. Is the purpose of this so that the $query variable is not changed when added modifiers are applied? How would the unverified users result be affected if the clone wasn't applied?
Would this be useful if i needed to call several groups of data for instance? Lets say, when i need to filter data based on users who are male or female. Would the base query pull all users, then the sub queries separate the two without additional calls to the database? Or is that something different?
I've had a few situations where i was querying the same table for different data sets and needed them to be individualized variables, and was wondering how to do so without multiple queries. Most of the times, I'd end up with a new query for each grouping, so i didnt think I was doing it right
Yes the purpose is so that the $query is not changed.
And your cases - it depends on the case, to be honest, there's no single recommended solution.
I never used clone() - just the same situations (not exactly the same xD) like in the video but without ->clone() and everything was fine.
The best once migrate --pretend, Thanks a lot
I love your youtube videos, I don't miss anyone. I follow you in Twitter, but Twitter shows a lot of feeds I don't whant. I dont see all your tweets.
I think most people don't read the documentation unless they're looking for a specific thing. Myself included
People not reading docs is a pain
Also in regards to the "clone" you should probably tell people what happens under the hood, meaning the way that memory is allocated. Cloning an object is something more advanced in the OOP section and a lot of people, either coming from bootcamps or university, don't know about. If you don't you will run in the problem that people on social media applaud you just because you sound smart
In regards to validating "nullable" vs "sometimes required", nullable from what i remember requires the key to exist in the payload but can have value null, while sometimes applied a isset check
great, thanks
really magic tips
It seems to me that tip 9 will not work and the sql query will still be executed, unless stopOnFirstFailure is called for the validator
Great tipps, but isn't the oposite of the "required" validation rule "prohibited"?
Not sure, please try and let me know :)
I'm not sure why/how it would be useful though. If you don't want the users to use that column, just remove it from the request. Or maybe even put it into the $guarded array.
@@kemal6039 It wasn't a question of how useful it is. But I, for example, have a few use cases for it, especially for transparency in admin panels when the form changes due to certain settings.
here for the algorithm ^^
That shows we are just too lazy to read documentation😅
we love it
some times i like. tips ..cause not time to read large tutorials to improve skills
Thanks!!!!
Lol I already know everything
The large number of likes for these kinds of tips likes show how many developers don’t read the Laravel docs 🤦🏻♂️
are you acoustic? when i liked this video, i don't read the docs? stfu dude.
liked for the content.
yeah, twitter is twitter, not X