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.

I'd personally love it if folks sharing Laravel tips could mention the version they're for. Makes life easier for everyone! 😄

Thanks a lot! Great tips and several of them are new for me! We want more! :)

I ve been working in Larvel for quite some time now and these tips come in very helpfull! Thank you so much grand master.

thank you for this video all of these tips didn't know any of them despite being in laravel documentation 24 / 7

nice, it shows how much information the documentation have that i will never find by myself 😆

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.

there are also methods abort_if and abort_unless, which are also shorten abort conditionals

The PEST architectural test tip is nice..... I would be interrested to know more what PEST can do.

Nice set of tips, thank you.

please do this format that was amazing

nice! and btw I agree it's twitter not "X"

I use twitter, I only subscribed on youtube. Thanks for sharing.

Thank you very much (from Uzbekistan, Fergana)

Yes tips ones are great !

here for the algorithm ^^

really magic tips

Know most of this but still i liked this concept of teaching 😀

Great tips, i knew only 5 tips)

I think most people don't read the documentation unless they're looking for a specific thing. Myself included

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.

great, thanks

we love it

Thanks!!!!

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

how beneficial (or not) is using clone for queries comparing to just working with the initial collection?

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

some times i like. tips ..cause not time to read large tutorials to improve skills

Sorry for my ignorance, but, is there some way to apply the second tip (arch tests), but using PHPUNIT instead of Pest?

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

Is the MAIL_DRIVER=log example still valid in LARAVEL 11? Because the default .env does not contain a MAIL_DRIVER entry...

Great tipps, but isn't the oposite of the "required" validation rule "prohibited"?

That shows we are just too lazy to read documentation😅

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 🤦🏻‍♂️

yeah, twitter is twitter, not X