User::setPassword() - Code Metrics - Inspection of "Добавлена возможность сохранять сущности с учетом..." - dimaxz/SimpleORM - Measure and Improve Code Quality continuously with Scrutinizer

Passed

Push — master ( de3595...5928a0 )

by dima

created 2015-12-16 14:45 UTC

User::setPassword() A

↳ Parent: User

Complexity

Conditions	1
Paths	1

Size

Total Lines	3
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	3
rs	10
cc	1
eloc	2
nc	1
nop	1

<?php
/*
 * To change this license header, choose License Headers in Project Properties.
 * To change this template file, choose Tools | Templates
 * and open the template in the editor.
 */

namespace Test\Domain\User;

use Test\Domain\UserGroup\UserGroup;

/**
 * Description of Producer
 *
 * @author d.lanec
 */
class User extends \SimpleORM\AbstractEntity {

	protected $email;
	protected $name;
	protected $password;
	protected $group;
	protected $address;
			
	function __construct($name, $email, $password, UserGroup $Group) {

		$this->setName($name);
		$this->setEmail($email);
		$this->setPassword($password);
		$this->setGroup($Group);
	}
	function getAddress() {

		return $this->address;
	}

	function setAddress($address) {

		$this->address = $address;
	}	
	
	function getEmail() {

		return $this->email;
	}

	function getName() {

		return $this->name;
	}

	function getPassword() {

		return $this->password;
	}

	function getGroup() {

		return $this->group;
	}

	function setEmail($email) {

		$this->email = $email;
	}

	function setName($name) {

		$this->name = $name;
	}

	function setPassword($password) {

		$this->password = $password;
	}

	function setGroup($group) {

		$this->group = $group;
	}


}


1			<?php
2			/*
3			* To change this license header, choose License Headers in Project Properties.
4			* To change this template file, choose Tools \| Templates
5			* and open the template in the editor.
6			*/
7
8			namespace Test\Domain\User;
9
10			use Test\Domain\UserGroup\UserGroup;
11
12			/**
13			* Description of Producer
14			*
15			* @author d.lanec
16			*/
17			class User extends \SimpleORM\AbstractEntity {
18
19			protected $email;
20			protected $name;
21			protected $password;
22			protected $group;
23			protected $address;
24
25			function __construct($name, $email, $password, UserGroup $Group) {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
26			$this->setName($name);
27			$this->setEmail($email);
28			$this->setPassword($password);
29			$this->setGroup($Group);
30			}
31			function getAddress() {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
32			return $this->address;
33			}
34
35			function setAddress($address) {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
36			$this->address = $address;
37			}
38
39			function getEmail() {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
40			return $this->email;
41			}
42
43			function getName() {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
44			return $this->name;
45			}
46
47			function getPassword() {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
48			return $this->password;
49			}
50
51			function getGroup() {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
52			return $this->group;
53			}
54
55			function setEmail($email) {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
56			$this->email = $email;
57			}
58
59			function setName($name) {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
60			$this->name = $name;
61			}
62
63			function setPassword($password) {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
64			$this->password = $password;
65			}
66
67			function setGroup($group) {
			0 ignored issues – show Best Practice introduced 2015-12-16 14:50 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
68			$this->group = $group;
69			}
70
71
72			}
73

dimaxz / SimpleORM

Push — master ( de3595...5928a0 )

User::setPassword() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like