1 | <?php |
||
2 | |||
3 | namespace humhub\modules\steam; |
||
4 | |||
5 | return [ |
||
6 | 'id' => 'steam', |
||
7 | 'class' => 'humhub\modules\steam\Module', |
||
8 | 'namespace' => 'humhub\modules\steam', |
||
9 | 'events' => [ |
||
10 | [ |
||
11 | 'class' => \humhub\modules\dashboard\widgets\Sidebar::class, |
||
0 ignored issues
–
show
|
|||
12 | 'event' => \humhub\modules\dashboard\widgets\Sidebar::EVENT_INIT, |
||
13 | 'callback' => [ |
||
14 | 'humhub\modules\steam\Events', |
||
15 | 'addSteamFrame' |
||
16 | ] |
||
17 | ], |
||
18 | [ |
||
19 | 'class' => \humhub\modules\space\widgets\Sidebar::class, |
||
0 ignored issues
–
show
The type
humhub\modules\space\widgets\Sidebar was not found. Maybe you did not declare it correctly or list all dependencies?
The issue could also be caused by a filter entry in the build configuration.
If the path has been excluded in your configuration, e.g. filter:
dependency_paths: ["lib/*"]
For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths ![]() |
|||
20 | 'event' => \humhub\modules\space\widgets\Sidebar::EVENT_INIT, |
||
21 | 'callback' => [ |
||
22 | 'humhub\modules\steam\Events', |
||
23 | 'addSteamFrame' |
||
24 | ] |
||
25 | ], |
||
26 | [ |
||
27 | 'class' => \humhub\modules\admin\widgets\AdminMenu::class, |
||
0 ignored issues
–
show
The type
humhub\modules\admin\widgets\AdminMenu was not found. Maybe you did not declare it correctly or list all dependencies?
The issue could also be caused by a filter entry in the build configuration.
If the path has been excluded in your configuration, e.g. filter:
dependency_paths: ["lib/*"]
For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths ![]() |
|||
28 | 'event' => \humhub\modules\admin\widgets\AdminMenu::EVENT_INIT, |
||
29 | 'callback' => [ |
||
30 | 'humhub\modules\steam\Events', |
||
31 | 'onAdminMenuInit' |
||
32 | ] |
||
33 | ] |
||
34 | ] |
||
35 | ]; |
||
36 | ?> |
||
0 ignored issues
–
show
It is not recommended to use PHP's closing tag
?> in files other than templates.
Using a closing tag in PHP files that only contain PHP code is not recommended as you might accidentally add whitespace after the closing tag which would then be output by PHP. This can cause severe problems, for example headers cannot be sent anymore. A simple precaution is to leave off the closing tag as it is not required, and it also has no negative effects whatsoever. ![]() |
|||
37 |
The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g.
excluded_paths: ["lib/*"]
, you can move it to the dependency path list as follows:For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths