![Cover image for Laravel Best Practice [Coding Standards Part 02] 🧑🦰👩🦰](https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6yz9vbo774q566mkrwqz.png)
Hello friends, This is the second article of Laravel coding standards article series.
If you didn't see the first article, I recommend to read it...
For further actions, you may consider blocking this person and/or reporting abuse
I'd like to add a thing to 02.
I've seen many devs use
envfunction.Please avoid
envand useconfiginstead.Because
.envfiles can be cached viaphp artisan config:cacheand you can't useenvfunction after that. (it will return null)So if any of the code uses
envfunction, you can't config cache in the future.great @bravemaster619 it's better to use config instep of env. and also we can use both.
we can use real content inside config file and. if we have local only thing we can use them inside .env .
like
"paypal_secret" = env("PAYPAL_SECRET" , 'asdfthdnejs323jn23nk3jn2njk3n2'),
and for our sandbox in local we can use key's inside .env
PAYPAL_SECRET = "kjansjnaknjsnalhjsbljhslhjlhjsla"
otherwise we don't want to use env anyware.
This.
Using
$request->all()is worst thing you can do. You should always use$request->validated().03 is more like: Avoid N+1 query problem.
Thank you for this post!🙏
I am about to start developing a project in Laravel and these tips will come in handy!
Thank you very much
Nice laravel tips, Lathindu.
Thank you very much.
Great post! Well done! Awesome to see some high-quality Laravel content on here!
Thanks man :)