These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
0 ignored issues
–
show
|
|||
2 | |||
3 | require_once __DIR__ . '/vendor/autoload.php'; |
||
4 | |||
5 | use smtech\StMarksReflexiveCanvasLTIExample\Toolbox; |
||
6 | use smtech\ReflexiveCanvasLTI\LTI\ToolProvider; |
||
7 | use Battis\DataUtilities; |
||
8 | |||
9 | define('CONFIG_FILE', __DIR__ . '/config.xml'); |
||
10 | define('CANVAS_INSTANCE_URL', 'canvas_instance_url'); |
||
11 | |||
12 | @session_start(); // TODO I don't feel good about suppressing warnings |
||
0 ignored issues
–
show
It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended.
If you suppress an error, we recommend checking for the error condition explicitly: // For example instead of
@mkdir($dir);
// Better use
if (@mkdir($dir) === false) {
throw new \RuntimeException('The directory '.$dir.' could not be created.');
}
![]() |
|||
13 | |||
14 | /* prepare the toolbox */ |
||
15 | if (empty($_SESSION[Toolbox::class])) { |
||
16 | $_SESSION[Toolbox::class] =& Toolbox::fromConfiguration(CONFIG_FILE); |
||
17 | } |
||
18 | $toolbox =& $_SESSION[Toolbox::class]; |
||
19 | $toolbox->smarty_prependTemplateDir(__DIR__ . '/templates', basename(__DIR__)); |
||
20 | $toolbox->smarty_assign([ |
||
21 | 'category' => DataUtilities::titleCase(preg_replace('/[\-_]+/', ' ', basename(__DIR__))) |
||
22 | ]); |
||
23 | |||
24 | /* set the Tool Consumer's instance URL, if present */ |
||
25 | if (empty($_SESSION[CANVAS_INSTANCE_URL]) && |
||
26 | !empty($_SESSION[ToolProvider::class]['canvas']['api_domain']) |
||
27 | ) { |
||
28 | $_SESSION[CANVAS_INSTANCE_URL] = 'https://' . $_SESSION[ToolProvider::class]['canvas']['api_domain']; |
||
29 | } |
||
30 |
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.