
Newton Job
@_newtonjob
Followers
4K
Following
14K
Media
588
Statuses
7K
Helping Laravel developers be **Laravel** developers. π₯· Master of #Laravel. π TALL | VILT | LEMP π’ Mathematician πΉ Keyboardist
Lagos, Nigeria
Joined September 2022
Pest 4 parallel browser testing really is a game-changer. The ability to run dozens of tests against a real browser simultaneously is just ridiculous.
2
8
99
In the past, you had to visit at least 3 different files to make these middleware settings that I just did with 3 lines of code. A testament to how far Laravel has come. π«Ά
2
6
102
Can someone tell me why JS folks love 2 spaces indentation? Not sure if it's just me, but I find it really hard to read.
36
0
106
So...I'm pretty sure that Pest 4 just solved every browser testing annoyance you've ever had. πΎ https://t.co/QM0u29Rpnh
8
24
178
Are you not using `MAIL_MAILER=log` and viewing your mails in the log viewer? you might just be missing out.
22
14
147
This would be a great @rectorphp set for @laravelphp π
When I'm reviewing a Laravel project, here are a few things I typically change at first sight. No compromise. Makes all the difference.
3
2
42
When I'm reviewing a Laravel project, here are a few things I typically change at first sight. No compromise. Makes all the difference.
20
34
457
Happy birthday to my amazing wife. She's made this past year the most special one yet as she became the most incredible mom. Love doing life with you! π©ββ€οΈβπ¨ Please say a prayer for her.
12
1
65
I realized that everyone that makes a comment like this, never tried the feature and so don't know how it works. Com'on guys, Laravel knows better than to load relationships that you don't need.
@_newtonjob A very bad idea when dealing with a large pool of data. You end up with data you donβt need when querying db hence just slowing down your app. I prefer to be selective when loading relationships.
5
1
30
Automatic eager loading + unguarded models should be the new defaults in every application. Realised I just can't live without them π€
17
14
177
If I remember correctly, this used to be the de facto (recommended?) configuration for database timestamps. Now we're all just creating nullable timestamps and handing them over to Eloquent. π€·ββοΈ
6
3
46
One of my biggest indecision moments. Should I keep the attribute or the scope?
21
4
68
I bet you're already doing this somehow. But in a non Laravelly-way π
Add your own constraints when Laravel tries to retrieve the Auth user.π In this example, we're making sure the user is not deactivated. Even if they were already logged in before deactivation, they will automatically be logged out.
7
6
58
Now I wish I knew this lots earlier. Really cook tip from @_newtonjob.
Add your own constraints when Laravel tries to retrieve the Auth user.π In this example, we're making sure the user is not deactivated. Even if they were already logged in before deactivation, they will automatically be logged out.
0
2
2
Add your own constraints when Laravel tries to retrieve the Auth user.π In this example, we're making sure the user is not deactivated. Even if they were already logged in before deactivation, they will automatically be logged out.
5
17
157