For what version of Laravel this best practices relevant?

[vanyabrovary]

For what version of Laravel this best practices?

[muhamadrafipamungkas]

in my opinion, if we look at the pattern, it seems to apply to the newest. Like most best practices which are always updated in general. But I'm also curious

[denizaygu]

Laravel5 onwards should support all of the practices listed.

[alexeymezenin]

I've created the repository for Laravel 5, but the practices are current. I guess I'll add more tips when I have time.

[SharakPL]

Laravel is on a highway in terms of development. I've only started to use L6 and it's L8 already. Maybe it would be best to add version numbers relevant to each practice.

BTW it would be great to have an extension for VSCode (and possibly other editors) to lint code based on best practices for used version apart from php common standards linted by phpcs or intelephense. Is there any of the kind being developed?

[JohnnyWalkerDigital]

People seeing rapid pace of Laravel often get freaked out (especially when they stumble into Jetstream and Tailwind and feel the world has been turned upside down), but the reality is that all of these best practices are equally valid for Laravel 5 through to 8.

I've just made the leap from 5 to 8... and after a few months I can confirm that (thankfully) things are NOT all that different. Everything here is still valid.

[andrzejkupczyk]

Maybe besides adding the "Interface" suffix which probably should be avoided if you take into account Laravel's codebase (vide contracts) or best practices collected here https://xqsit.github.io/laravel-coding-guidelines/docs/naming-conventions/ or https://www.mindtwo.de/guidelines/coding/laravel. There's already plenty of articles about this one:
https://verraes.net/2013/09/sensible-interfaces/
https://www.nikolaposa.in.rs/blog/2019/01/06/better-naming-convention/
https://www.alainschlesser.com/interface-naming-conventions/
https://phpixie.com/blog/naming-interfaces-in-php.html