Conditions | 1 |
Paths | 1 |
Total Lines | 12 |
Code Lines | 7 |
Lines | 0 |
Ratio | 0 % |
Changes | 0 |
1 | <?php |
||
20 | public function boot() |
||
21 | { |
||
22 | $this->publishes([ |
||
23 | __DIR__ . '/config/laravel-google-structured-data-testing-tool.php' => config_path('laravel-google-structured-data-testing-tool.php'), |
||
24 | ], 'config'); |
||
25 | |||
26 | $this->loadViewsFrom(__DIR__ . '/views', 'laravel-google-structured-data-testing-tool'); |
||
27 | |||
28 | $this->publishes([ |
||
29 | __DIR__ . '/views' => base_path('resources/views/vendor/laravel-google-structured-data-testing-tool'), |
||
30 | ]); |
||
31 | } |
||
32 | |||
72 |
PHP Analyzer performs a side-effects analysis of your code. A side-effect is basically anything that might be visible after the scope of the method is left.
Let’s take a look at an example:
If we look at the
getEmail()
method, we can see that it has no side-effect. Whether you call this method or not, no future calls to other methods are affected by this. As such code as the following is useless:On the hand, if we look at the
setEmail()
, this method _has_ side-effects. In the following case, we could not remove the method call: