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

BeforeDeleteTrashItemEvent::setResult()   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\Trash;
6
7
use eZ\Publish\API\Repository\Values\Content\TrashItem;
8
use eZ\Publish\API\Repository\Values\Content\Trash\TrashItemDeleteResult;
9
use eZ\Publish\Core\Event\BeforeEvent;
10
11
final class BeforeDeleteTrashItemEvent extends BeforeEvent
12
{
13
	public const NAME = 'ezplatform.event.trash.item_delete.before';
14
15
	/**
16
     * @var \eZ\Publish\API\Repository\Values\Content\TrashItem
17
     */
18
	private $trashItem;
19
20
	/**
21
     * @var \eZ\Publish\API\Repository\Values\Content\Trash\TrashItemDeleteResult|null
22
     */
23
	private $result;
24
25
26
	public function __construct(TrashItem $trashItem)
27
	{
28
		$this->trashItem = $trashItem;
29
	}
30
31
32
	public function getTrashItem(): TrashItem
33
	{
34
		return $this->trashItem;
35
	}
36
37
38
	function getResult(): ?TrashItemDeleteResult
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->result;
41
	}
42
43
44
	function setResult(?TrashItemDeleteResult $result): 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->result = $result;
47
	}
48
49
50
	function hasResult(): 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->result instanceof TrashItemDeleteResult;
53
	}
54
}
55