Completed
Push — ezp-30616 ( ab7e14...128c78 )
by
unknown
17:09
created

BeforeUpdateUserEvent   A

Complexity

Total Complexity 6

Size/Duplication

Total Lines 56
Duplicated Lines 0 %

Coupling/Cohesion

Components 1
Dependencies 1

Importance

Changes 0
Metric Value
dl 0
loc 56
rs 10
c 0
b 0
f 0
wmc 6
lcom 1
cbo 1

6 Methods

Rating   Name   Duplication   Size   Complexity  
A __construct() 0 5 1
A getUser() 0 4 1
A getUserUpdateStruct() 0 4 1
A getUpdatedUser() 0 4 1
A setUpdatedUser() 0 4 1
A hasUpdatedUser() 0 4 1
1
<?php
2
3
declare(strict_types=1);
4
5
namespace eZ\Publish\Core\Event\User;
6
7
use eZ\Publish\API\Repository\Values\User\User;
8
use eZ\Publish\API\Repository\Values\User\UserUpdateStruct;
9
use eZ\Publish\Core\Event\BeforeEvent;
10
11
final class BeforeUpdateUserEvent extends BeforeEvent
12
{
13
	public const NAME = 'ezplatform.event.user.update.before';
14
15
	/**
16
     * @var \eZ\Publish\API\Repository\Values\User\User
17
     */
18
	private $user;
19
20
	/**
21
     * @var \eZ\Publish\API\Repository\Values\User\UserUpdateStruct
22
     */
23
	private $userUpdateStruct;
24
25
	/**
26
     * @var \eZ\Publish\API\Repository\Values\User\User|null
27
     */
28
	private $updatedUser;
29
30
31
	public function __construct(User $user, UserUpdateStruct $userUpdateStruct)
32
	{
33
		$this->user = $user;
34
		$this->userUpdateStruct = $userUpdateStruct;
35
	}
36
37
38
	public function getUser(): User
39
	{
40
		return $this->user;
41
	}
42
43
44
	public function getUserUpdateStruct(): UserUpdateStruct
45
	{
46
		return $this->userUpdateStruct;
47
	}
48
49
50
	function getUpdatedUser(): ?User
0 ignored issues
show
Best Practice introduced by
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...
51
	{
52
		return $this->updatedUser;
53
	}
54
55
56
	function setUpdatedUser(?User $updatedUser): void
0 ignored issues
show
Best Practice introduced by
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...
57
	{
58
		$this->updatedUser = $updatedUser;
59
	}
60
61
62
	function hasUpdatedUser(): bool
0 ignored issues
show
Best Practice introduced by
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...
63
	{
64
		return $this->updatedUser instanceof User;
65
	}
66
}
67