Completed
Push — master ( b6e787...12bc8e )
by Bram
03:41
created

CheckInValidator::validate()   C

Complexity

Conditions 9
Paths 12

Size

Total Lines 59
Code Lines 33

Duplication

Lines 14
Ratio 23.73 %

Importance

Changes 0
Metric Value
dl 14
loc 59
rs 6.9133
c 0
b 0
f 0
cc 9
eloc 33
nc 12
nop 1

How to fix   Long Method   

Long Method

Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.

For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.

Commonly applied refactorings include:

1
<?php
2
3
namespace Broarm\EventTickets;
4
5
use Object;
6
7
/**
8
 * CheckInValidator.php
9
 *
10
 * @author Bram de Leeuw
11
 * Date: 14/06/2017
12
 */
13
class CheckInValidator extends Object
14
{
15
    const MESSAGE_ERROR = 'MESSAGE_ERROR';
16
    const MESSAGE_NO_CODE = 'MESSAGE_NO_CODE';
17
    const MESSAGE_CODE_NOT_FOUND = 'MESSAGE_CODE_NOT_FOUND';
18
    const MESSAGE_TICKET_CANCELLED = 'MESSAGE_TICKET_CANCELLED';
19
    const MESSAGE_ALREADY_CHECKED_IN = 'MESSAGE_ALREADY_CHECKED_IN';
20
    const MESSAGE_CHECK_OUT_SUCCESS = 'MESSAGE_CHECK_OUT_SUCCESS';
21
    const MESSAGE_CHECK_IN_SUCCESS = 'MESSAGE_CHECK_IN_SUCCESS';
22
23
    const MESSAGE_TYPE_GOOD = 'Good';
24
    const MESSAGE_TYPE_WARNING = 'Warning';
25
    const MESSAGE_TYPE_BAD = 'Bad';
26
27
    /**
28
     * Allow people to check in and out
29
     *
30
     * @config
31
     * @var bool
32
     */
33
    private static $allow_checkout = false;
0 ignored issues
show
Unused Code introduced by
The property $allow_checkout is not used and could be removed.

This check marks private properties in classes that are never used. Those properties can be removed.

Loading history...
34
35
    /**
36
     * @var Attendee
37
     */
38
    protected $attendee = null;
39
40
    /**
41
     * Validate the given ticket code
42
     *
43
     * @param null|string $ticketCode
44
     *
45
     * @return array
46
     */
47
    public function validate($ticketCode = null)
48
    {
49
        if (filter_var($ticketCode, FILTER_VALIDATE_URL)) {
50
            $asURL = explode('/', parse_url($ticketCode, PHP_URL_PATH));
51
            $ticketCode = end($asURL);
52
        }
53
        
54
        // Check if a code is given to the validator
55
        if (!isset($ticketCode)) {
56
            return array(
57
                'Code' => self::MESSAGE_NO_CODE,
58
                'Message' => self::message(self::MESSAGE_NO_CODE),
59
                'Type' => self::MESSAGE_TYPE_BAD
60
            );
61
        }
62
63
        // Check if a ticket exists with the given ticket code
64
        if (!$this->attendee = Attendee::get()->find('TicketCode', $ticketCode)) {
0 ignored issues
show
Documentation Bug introduced by
It seems like \Broarm\EventTickets\Att...cketCode', $ticketCode) can also be of type object<DataObject>. However, the property $attendee is declared as type object<Broarm\EventTickets\Attendee>. Maybe add an additional type check?

Our type inference engine has found a suspicous assignment of a value to a property. This check raises an issue when a value that can be of a mixed type is assigned to a property that is type hinted more strictly.

For example, imagine you have a variable $accountId that can either hold an Id object or false (if there is no account id yet). Your code now assigns that value to the id property of an instance of the Account class. This class holds a proper account, so the id value must no longer be false.

Either this assignment is in error or a type check should be added for that assignment.

class Id
{
    public $id;

    public function __construct($id)
    {
        $this->id = $id;
    }

}

class Account
{
    /** @var  Id $id */
    public $id;
}

$account_id = false;

if (starsAreRight()) {
    $account_id = new Id(42);
}

$account = new Account();
if ($account instanceof Id)
{
    $account->id = $account_id;
}
Loading history...
65
            return array(
66
                'Code' => self::MESSAGE_CODE_NOT_FOUND,
67
                'Message' => self::message(self::MESSAGE_CODE_NOT_FOUND),
68
                'Type' => self::MESSAGE_TYPE_BAD
69
            );
70
        }
71
72
        // Check if the reservation is not canceled
73
        if (!(bool)$this->attendee->Event()->getGuestList()->find('ID', $this->attendee->ID)) {
74
            return array(
75
                'Code' => self::MESSAGE_TICKET_CANCELLED,
76
                'Message' => self::message(self::MESSAGE_TICKET_CANCELLED),
77
                'Type' => self::MESSAGE_TYPE_BAD
78
            );
79
        }
80
81
        // Check if the ticket is already checked in and not allowed to check out
82 View Code Duplication
        elseif ((bool)$this->attendee->CheckedIn && !(bool)self::config()->get('allow_checkout')) {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
83
            return array(
84
                'Code' => self::MESSAGE_ALREADY_CHECKED_IN,
85
                'Message' => self::message(self::MESSAGE_ALREADY_CHECKED_IN),
86
                'Type' => self::MESSAGE_TYPE_BAD
87
            );
88
        }
89
90
        // Successfully checked out
91 View Code Duplication
        elseif ((bool)$this->attendee->CheckedIn && (bool)self::config()->get('allow_checkout')) {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
92
            return array(
93
                'Code' => self::MESSAGE_CHECK_OUT_SUCCESS,
94
                'Message' => self::message(self::MESSAGE_CHECK_OUT_SUCCESS),
95
                'Type' => self::MESSAGE_TYPE_WARNING
96
            );
97
        }
98
99
        // Successfully checked in
100
        else return array(
101
            'Code' => self::MESSAGE_CHECK_IN_SUCCESS,
102
            'Message' => self::message(self::MESSAGE_CHECK_IN_SUCCESS),
103
            'Type' => self::MESSAGE_TYPE_GOOD
104
        );
105
    }
106
107
    /**
108
     * Get the attendee instance
109
     *
110
     * @return Attendee
111
     */
112
    public function getAttendee()
113
    {
114
        return $this->attendee;
115
    }
116
117
    /**
118
     * Translate the given type to a readable message
119
     *
120
     * @param $message string
121
     *
122
     * @return string
123
     */
124
    private static function message($message) {
125
        return _t("CheckInValidator.$message", $message);
126
    }
127
}