RecordNotFoundException::message() - Code Metrics - andela-sakande/potatoORM - Measure and Improve Code Quality continuously with Scrutinizer

RecordNotFoundException::message() A
last analyzed 2015-11-26 11:01 UTC

↳ Parent: RecordNotFoundException

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

<?php

/**
 * @package A simple ORM that performs basic CRUD operations
 * @author Surajudeen AKANDE <[email protected]>
 * @license MIT <https://opensource.org/licenses/MIT>
 * @link http://www.github.com/andela-sakande
 * */
namespace Sirolad\Exceptions;

/**
 * Exception class for Inexistent Record
 * */
use PDOException;

class RecordNotFoundException extends PDOException
{
     /**
     * constructor class
     * */
    public function __construct()
    {
        $this->message();
class User
{
    private $email;

    public function getEmail()
    {
        return $this->email;
    }

    public function setEmail($email)
    {
        $this->email = $email;
    }
}
    }

    /**
     * @return string
     * */
    public function message()
    {
        return 'Fatal Error: This record does not exist';
    }
}


1			<?php
2
3			/**
4			* @package A simple ORM that performs basic CRUD operations
5			* @author Surajudeen AKANDE <[email protected]>
6			* @license MIT <https://opensource.org/licenses/MIT>
7			* @link http://www.github.com/andela-sakande
8			* */
9			namespace Sirolad\Exceptions;
10
11			/**
12			* Exception class for Inexistent Record
13			* */
14			use PDOException;
15
16			class RecordNotFoundException extends PDOException
17			{
18			/**
19			* constructor class
20			* */
21			public function __construct()
22			{
23			$this->message();
			0 ignored issues – show Unused Code introduced 2015-11-26 11:01 UTC by Report Bug Copy Issue Report The call to the method `Sirolad\Exceptions\Recor...undException::message()` seems un-needed as the method has no side-effects. PHP Analyzer performs a side-effects analysis of your code. A side-effect is basically anything that might be visible after the scope of the method is left. Let’s take a look at an example: class User { private $email; public function getEmail() { return $this->email; } public function setEmail($email) { $this->email = $email; } } If we look at the `getEmail()` method, we can see that it has no side-effect. Whether you call this method or not, no future calls to other methods are affected by this. As such code as the following is useless: $user = new User(); $user->getEmail(); // This line could safely be removed as it has no effect. On the hand, if we look at the `setEmail()`, this method _has_ side-effects. In the following case, we could not remove the method call: $user = new User(); $user->setEmail('email@domain'); // This line has a side-effect (it changes an // instance variable). Loading history...
24			}
25
26			/**
27			* @return string
28			* */
29			public function message()
30			{
31			return 'Fatal Error: This record does not exist';
32			}
33			}
34

andela-sakande / potatoORM

RecordNotFoundException::message() A last analyzed 2015-11-26 11:01 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

RecordNotFoundException::message() A
last analyzed 2015-11-26 11:01 UTC