__bootstrap accesses the super-global variable $_SERVER. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
__bootstrap accesses the super-global variable $_COOKIE. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
destroy accesses the super-global variable $_SESSION. Open
public function destroy($key = null)
{
if (isset($key)) {
if ($this->has($key)) {
$_SESSION[$this->_namespace][$key] = null;
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
hash accesses the super-global variable $_SESSION. Open
public function hash()
{
return serialize($_SESSION[$this->_namespace]);
}
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
has accesses the super-global variable $_SESSION. Open
public function has($key)
{
if (!isset($this->_data[$key]) && isset($_SESSION[$this->_namespace][$key])) {
$this->set($key, $_SESSION[$this->_namespace][$key]);
}
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
__bootstrap accesses the super-global variable $_SERVER. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
__bootstrap accesses the super-global variable $_SESSION. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
has accesses the super-global variable $_SESSION. Open
public function has($key)
{
if (!isset($this->_data[$key]) && isset($_SESSION[$this->_namespace][$key])) {
$this->set($key, $_SESSION[$this->_namespace][$key]);
}
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
__bootstrap accesses the super-global variable $_SESSION. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
__bootstrap accesses the super-global variable $_SESSION. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
__bootstrap accesses the super-global variable $_SERVER. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
__bootstrap accesses the super-global variable $_SERVER. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
destroy accesses the super-global variable $_SESSION. Open
public function destroy($key = null)
{
if (isset($key)) {
if ($this->has($key)) {
$_SESSION[$this->_namespace][$key] = null;
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
__bootstrap accesses the super-global variable $_SESSION. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
set accesses the super-global variable $_SESSION. Open
public function set($key, $value)
{
parent::set($key, $value);
if ($value instanceof Ajde_Model) {
// TODO:
- Read upRead up
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
Method __bootstrap
has 54 lines of code (exceeds 25 allowed). Consider refactoring. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
Function __bootstrap
has a Cognitive Complexity of 16 (exceeds 5 allowed). Consider refactoring. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
Cognitive Complexity
Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.
A method's cognitive complexity is based on a few simple rules:
- Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
- Code is considered more complex for each "break in the linear flow of the code"
- Code is considered more complex when "flow breaking structures are nested"
Further reading
The method __bootstrap() has 103 lines of code. Current threshold is set to 100. Avoid really long methods. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Exclude checks
The method __bootstrap() has a Cyclomatic Complexity of 12. The configured cyclomatic complexity threshold is 10. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
CyclomaticComplexity
Since: 0.1
Complexity is determined by the number of decision points in a method plus one for the method entry. The decision points are 'if', 'while', 'for', and 'case labels'. Generally, 1-4 is low complexity, 5-7 indicates moderate complexity, 8-10 is high complexity, and 11+ is very high complexity.
Example
// Cyclomatic Complexity = 11
class Foo {
1 public function example() {
2 if ($a == $b) {
3 if ($a1 == $b1) {
fiddle();
4 } elseif ($a2 == $b2) {
fiddle();
} else {
fiddle();
}
5 } elseif ($c == $d) {
6 while ($c == $d) {
fiddle();
}
7 } elseif ($e == $f) {
8 for ($n = 0; $n < $h; $n++) {
fiddle();
}
} else {
switch ($z) {
9 case 1:
fiddle();
break;
10 case 2:
fiddle();
break;
11 case 3:
fiddle();
break;
default:
fiddle();
break;
}
}
}
}
Source https://phpmd.org/rules/codesize.html#cyclomaticcomplexity
Missing class import via use statement (line '70', column '30'). Open
$exception = new Ajde_Core_Exception_Security('Possible session hijacking detected. Bailing out.');
- Read upRead up
- Exclude checks
MissingImport
Since: 2.7.0
Importing all external classes in a file through use statements makes them clearly visible.
Example
function make() {
return new \stdClass();
}
Source http://phpmd.org/rules/cleancode.html#MissingImport
Missing class import via use statement (line '161', column '23'). Open
throw new Ajde_Exception('It is not allowed to store a Model directly in the session, use Ajde_Session::setModel() instead.');
- Read upRead up
- Exclude checks
MissingImport
Since: 2.7.0
Importing all external classes in a file through use statements makes them clearly visible.
Example
function make() {
return new \stdClass();
}
Source http://phpmd.org/rules/cleancode.html#MissingImport
Avoid using static access to class 'Ajde_Exception_Log' in method '__bootstrap'. Open
Ajde_Exception_Log::logException($exception);
- Read upRead up
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
The method destroy uses an else expression. Else clauses are basically not necessary and you can simplify the code by not using them. Open
} else {
$_SESSION[$this->_namespace] = null;
$this->reset();
}
- Read upRead up
- Exclude checks
ElseExpression
Since: 1.4.0
An if expression with an else branch is basically not necessary. You can rewrite the conditions in a way that the else clause is not necessary and the code becomes simpler to read. To achieve this, use early return statements, though you may need to split the code it several smaller methods. For very simple assignments you could also use the ternary operations.
Example
class Foo
{
public function bar($flag)
{
if ($flag) {
// one branch
} else {
// another branch
}
}
}
Source https://phpmd.org/rules/cleancode.html#elseexpression
Avoid using static access to class 'Ajde_Dump' in method 'getModel'. Open
Ajde_Dump::warn('Model definition changed during session');
- Read upRead up
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
The method __bootstrap uses an else expression. Else clauses are basically not necessary and you can simplify the code by not using them. Open
} else {
$_SESSION['client'] = md5($remoteIp.issetor($_SERVER['HTTP_USER_AGENT']).config('security.secret'));
if ($lifetime > 0) {
// Force send new cookie with updated lifetime (forcing keep-alive)
- Read upRead up
- Exclude checks
ElseExpression
Since: 1.4.0
An if expression with an else branch is basically not necessary. You can rewrite the conditions in a way that the else clause is not necessary and the code becomes simpler to read. To achieve this, use early return statements, though you may need to split the code it several smaller methods. For very simple assignments you could also use the ternary operations.
Example
class Foo
{
public function bar($flag)
{
if ($flag) {
// one branch
} else {
// another branch
}
}
}
Source https://phpmd.org/rules/cleancode.html#elseexpression
The method __bootstrap uses an else expression. Else clauses are basically not necessary and you can simplify the code by not using them. Open
} else {
// don't redirect/log for resource items, as they should have no side effect
// this makes it possible for i.e. web crawlers/error pages to view resources
$request = Ajde_Http_Request::fromGlobal();
$route = $request->initRoute();
- Read upRead up
- Exclude checks
ElseExpression
Since: 1.4.0
An if expression with an else branch is basically not necessary. You can rewrite the conditions in a way that the else clause is not necessary and the code becomes simpler to read. To achieve this, use early return statements, though you may need to split the code it several smaller methods. For very simple assignments you could also use the ternary operations.
Example
class Foo
{
public function bar($flag)
{
if ($flag) {
// one branch
} else {
// another branch
}
}
}
Source https://phpmd.org/rules/cleancode.html#elseexpression
Avoid using static access to class 'Ajde_Http_Request' in method '__bootstrap'. Open
$remoteIp = Ajde_Http_Request::getClientIP();
- Read upRead up
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class 'Ajde_Http_Request' in method '__bootstrap'. Open
$request = Ajde_Http_Request::fromGlobal();
- Read upRead up
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
TODO found Open
// TODO:
- Exclude checks
TODO found Open
// TODO:
- Exclude checks
TODO found Open
// TODO: overhead to call session_regenerate_id? is it not required??
- Exclude checks
TODO found Open
// @todo TODO: security issue!!
- Exclude checks
The class Ajde_Session is not named in CamelCase. Open
class Ajde_Session extends Ajde_Object_Standard
{
protected $_namespace = null;
public function __bootstrap()
- Read upRead up
- Exclude checks
CamelCaseClassName
Since: 0.2
It is considered best practice to use the CamelCase notation to name classes.
Example
class class_name {
}
Source
The property $_namespace is not named in camelCase. Open
class Ajde_Session extends Ajde_Object_Standard
{
protected $_namespace = null;
public function __bootstrap()
- Read upRead up
- Exclude checks
CamelCasePropertyName
Since: 0.2
It is considered best practice to use the camelCase notation to name attributes.
Example
class ClassName {
protected $property_name;
}
Source
The method __bootstrap is not named in camelCase. Open
public function __bootstrap()
{
// Session name
$sessionName = config('app.id').'_session';
session_name($sessionName);
- Read upRead up
- Exclude checks
CamelCaseMethodName
Since: 0.2
It is considered best practice to use the camelCase notation to name methods.
Example
class ClassName {
public function get_name() {
}
}