Should the return type not be boolean|string|null?
This check compares the return type specified in the @return annotation of a function
or method doc comment with the types returned by the function and raises an issue if they
mismatch.
Loading history...
23
*/
24
public function addProtectionWarningToOutput(OutputInterface $output)
25
{
26
$checker = new SuperSakeChecker();
27
if ((bool) $checker->superSakeIsNotProtected()) {
28
$output->writeln("\n");
29
$output->writeln('<error>The supersake file is accessible by browsers</error>');
30
$output->writeln('<error>Please lock down the file by either : </error>');
31
$output->writeln('<comment>Adding this to your .htaccess file</comment>');
32
$output->writeln($checker->htaccessContent());
33
$output->writeln('<comment>Or add this to the <fileExtensions allowUnlisted="true"> section of your web.config file if you are running on iis</comment>');
34
$output->writeln($checker->webconfigContent());
35
$output->writeln("\n");
36
$output->writeln('<comment>Or run $ `php supersake protect` to write these lines to the files</comment>');
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.