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

BeforeCreateRoleDraftEvent::getRoleDraft()   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 0
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\Role;
8
use eZ\Publish\API\Repository\Values\User\RoleDraft;
9
use eZ\Publish\Core\Event\BeforeEvent;
10
11
final class BeforeCreateRoleDraftEvent extends BeforeEvent
12
{
13
	public const NAME = 'ezplatform.event.role.draft_create.before';
14
15
	/**
16
     * @var \eZ\Publish\API\Repository\Values\User\Role
17
     */
18
	private $role;
19
20
	/**
21
     * @var \eZ\Publish\API\Repository\Values\User\RoleDraft|null
22
     */
23
	private $roleDraft;
24
25
26
	public function __construct(Role $role)
27
	{
28
		$this->role = $role;
29
	}
30
31
32
	public function getRole(): Role
33
	{
34
		return $this->role;
35
	}
36
37
38
	function getRoleDraft(): ?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...
39
	{
40
		return $this->roleDraft;
41
	}
42
43
44
	function setRoleDraft(?RoleDraft $roleDraft): 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...
45
	{
46
		$this->roleDraft = $roleDraft;
47
	}
48
49
50
	function hasRoleDraft(): 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...
51
	{
52
		return $this->roleDraft instanceof RoleDraft;
53
	}
54
}
55