Overview
(0 errors, 0 warnings)
This section shows the general problems detected when processing the code [More info]
PHP lint problems
(0 errors, 0 warnings)
This section shows php lint problems in the code detected by php -l [More info]
PHP coding style problems
(61 errors, 0 warnings)
This section shows the coding style problems detected in the code by phpcs [More info]
- admin/tool/clearbackupfiles/classes/event/clearbackup_completed.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/classes/event/coursebackup_removed.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/classes/privacy/provider.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/classes/processer.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/classes/task/cron_task.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/confirm_form.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/db/tasks.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/index.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/lang/en/tool_clearbackupfiles.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- (#25) Unexpected string end, it should be a line feed after a semicolon
- (#26) Unexpected string end, it should be a line feed after a semicolon
- (#28) Unexpected string end, it should be a line feed after a semicolon
- (#29) Unexpected string end, it should be a line feed after a semicolon
- (#30) Unexpected string end, it should be a line feed after a semicolon
- (#32) Unexpected string end, it should be a line feed after a semicolon
- (#33) Unexpected string end, it should be a line feed after a semicolon
- (#35) Unexpected string end, it should be a line feed after a semicolon
- (#36) Unexpected string end, it should be a line feed after a semicolon
- (#38) Unexpected string end, it should be a line feed after a semicolon
- (#39) Unexpected string end, it should be a line feed after a semicolon
- (#40) Unexpected string end, it should be a line feed after a semicolon
- (#41) Unexpected string end, it should be a line feed after a semicolon
- (#42) Unexpected string end, it should be a line feed after a semicolon
- (#44) Unexpected string end, it should be a line feed after a semicolon
- (#46) Unexpected string end, it should be a line feed after a semicolon
- (#47) Unexpected string end, it should be a line feed after a semicolon
- admin/tool/clearbackupfiles/settings.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
- admin/tool/clearbackupfiles/version.php
- (#1) End of line character is invalid; expected "\n" but found "\r\n"
- (#3) Line 2 of the opening comment must start "//".
- (#8) Line 7 of the opening comment must start "//".
- (#13) Line 12 of the opening comment must start "//".
Javascript coding style problems
(0 errors, 0 warnings)
This section shows the coding style problems detected in the code by eslint [More info]
CSS problems
(0 errors, 0 warnings)
This section shows CSS problems detected by stylelint [More info]
PHPDocs style problems
(0 errors, 0 warnings)
This section shows the phpdocs problems detected in the code by local_moodlecheck [More info]
Update savepoints problems
(0 errors, 0 warnings)
This section shows problems detected with the handling of upgrade savepoints [More info]
Third party library modification problems
(0 errors, 0 warnings)
This section shows problems detected with the modification of third party libraries [More info]
grunt changes
(0 errors, 0 warnings)
This section shows files built by grunt and not commited [More info]
shifter problems
(0 errors, 0 warnings)
This section shows problems detected by shifter [More info]
Mustache template problems
(0 errors, 0 warnings)
This section shows problems detected in mustache templates [More info]
Gherkin .feature problems
(0 errors, 0 warnings)
This section shows problems detected in behat .feature files [More info]