🔥 This week's code tips for Laravel developers
🧵 A weekly thread
8
❌ To customise a validation message for a request in @laravelphp , you can add a message function to a form request. Very handy!
#laravel #php
7
🔥Another amazing #Laravel feature!🔥
We often write if statements to check if a value is present on a request or not.
You can simplify it with the whenFilled() helper.
👋If you find this useful, consider clicking the button that says Retweet. It's a very cool button!
6
Does your @laravelphp application have 0 tests? Here is one test you can easily add to get started. It's probably the most important test — in web projects — and it has an enormous value.
✓ Ensures your application boots. ✅ ✓ Ensures the home page can be loaded. 💨
5
If you’re returning a fully qualified class name, you can use the class-name docblock. You can specify a base class or interface between <>
And of course, you can also return an array of class-names too 👍
#php
4
This pattern is brilliant and can make your code much more clean and consistent
The tweet is from last year, but it's still very relevant
3
⚡️ Database Tip
You don't have to execute multiple queries to calculate different aggregates. With the filter clause you can narrow the rows which should be included for the calculation. So you may need to scan the table only once, the performance impact can be massive 🔥
2
🔥 Simple typehints and annotations go a long way
Even without any docblocks, this code is perfectly understandable by both developers and IDEs
Writing code like this: 👉 Prevents bugs using type safety 👉 Makes the code self-documenting 👉 Takes only a few seconds to implement
1
🔥 I often find myself keeping validation rules in a method on the model. This lets me reuse them wherever I may need - including in controllers or form requests.
We're writing a book, you can get it for free here. We're writing a book! Join the early access to get it for free.