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

BeforeUpdateRoleDraftEvent::setUpdatedRoleDraft()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
nc 1
nop 1
dl 0
loc 4
rs 10
c 0
b 0
f 0
1
<?php
2
3
declare(strict_types=1);
4
5
namespace eZ\Publish\Core\Event\Role;
6
7
use eZ\Publish\API\Repository\Values\User\RoleDraft;
8
use eZ\Publish\API\Repository\Values\User\RoleUpdateStruct;
9
use eZ\Publish\Core\Event\BeforeEvent;
10
11
final class BeforeUpdateRoleDraftEvent extends BeforeEvent
12
{
13
	public const NAME = 'ezplatform.event.role.draft_update.before';
14
15
	/**
16
     * @var \eZ\Publish\API\Repository\Values\User\RoleDraft
17
     */
18
	private $roleDraft;
19
20
	/**
21
     * @var \eZ\Publish\API\Repository\Values\User\RoleUpdateStruct
22
     */
23
	private $roleUpdateStruct;
24
25
	/**
26
     * @var \eZ\Publish\API\Repository\Values\User\RoleDraft|null
27
     */
28
	private $updatedRoleDraft;
29
30
31
	public function __construct(RoleDraft $roleDraft, RoleUpdateStruct $roleUpdateStruct)
32
	{
33
		$this->roleDraft = $roleDraft;
34
		$this->roleUpdateStruct = $roleUpdateStruct;
35
	}
36
37
38
	public function getRoleDraft(): RoleDraft
39
	{
40
		return $this->roleDraft;
41
	}
42
43
44
	public function getRoleUpdateStruct(): RoleUpdateStruct
45
	{
46
		return $this->roleUpdateStruct;
47
	}
48
49
50
	function getUpdatedRoleDraft(): ?RoleDraft
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->updatedRoleDraft;
53
	}
54
55
56
	function setUpdatedRoleDraft(?RoleDraft $updatedRoleDraft): 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->updatedRoleDraft = $updatedRoleDraft;
59
	}
60
61
62
	function hasUpdatedRoleDraft(): 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->updatedRoleDraft instanceof RoleDraft;
65
	}
66
}
67