If you right click on the file and select “Inspect code…” PhpStorm presents a list of the warnings. This is even more helpful for classes that do not fit on a screen.īTW: I prefer using the explicit facades over the aliases (I’m not using the explicit facade for “App” here, I will explain the reason for that later on). You can see the colour-coded level of the worst warning in the upper right corner. For this the IDE is building an internal model of the code using static code analysis. They are caused by the inspections in PhpStorm. So let’s take a look at an exemplary Laravel controller. In this article, I’ll show you how you can leverage the power of the PhpStorm inspections for your Laravel projects. The inspections of PhpStorm are being improved with every new release. If I manage to get all inspections on a file to pass, I see a lot of issues right away. Otherwise I would be prone to the “broken window theory”. Therefore I’d like to keep all inspections “green”. I’d like to see potential issues in my projects right away by looking at the source code.
0 kommentar(er)
