Completed
Pull Request — master (#48)
by Patrick
02:22
created

FVSPlugin::get_plugin_entry_point()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 0 Features 0
Metric Value
c 1
b 0
f 0
dl 0
loc 4
rs 10
cc 1
eloc 2
nc 1
nop 0
1
<?php
2
/*
0 ignored issues
show
Unused Code Comprehensibility introduced by
58% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
3
class FVSPlugin extends SecurePlugin
4
{
5
    function get_secure_menu_entries($page, $user)
6
    {
7
        $ret = array('Volunteer'=>$page->secure_root.'fvs/index.php');
8
        return $ret;
9
    }
10
11
    function get_plugin_entry_point()
12
    {
13
        return array('name'=>'Volunteer', 'link'=>'fvs/index.php');
14
    }
15
}
16
*/
17
?>
0 ignored issues
show
Best Practice introduced by
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.

Loading history...
18