This project does not seem to handle request data directly as such no vulnerable execution paths were found.
include
, or for example
via PHP's auto-loading mechanism.
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | namespace Gueststream\PMS\IQWare\API; |
||
4 | |||
5 | class Reservations |
||
6 | { |
||
7 | |||
8 | /** |
||
9 | * @var int $ConfirmationNo |
||
10 | */ |
||
11 | protected $ConfirmationNo = null; |
||
12 | |||
13 | /** |
||
14 | * @var string $Name |
||
15 | */ |
||
16 | protected $Name = null; |
||
17 | |||
18 | /** |
||
19 | * @var \DateTime $CreationDate |
||
20 | */ |
||
21 | protected $CreationDate = null; |
||
22 | |||
23 | /** |
||
24 | * @var \DateTime $ArrivalDate |
||
25 | */ |
||
26 | protected $ArrivalDate = null; |
||
27 | |||
28 | /** |
||
29 | * @var \DateTime $DepartureDate |
||
30 | */ |
||
31 | protected $DepartureDate = null; |
||
32 | |||
33 | /** |
||
34 | * @var int $AccountStatus |
||
35 | */ |
||
36 | protected $AccountStatus = null; |
||
37 | |||
38 | /** |
||
39 | * @param int $ConfirmationNo |
||
40 | * @param string $Name |
||
41 | * @param \DateTime $CreationDate |
||
42 | * @param \DateTime $ArrivalDate |
||
43 | * @param \DateTime $DepartureDate |
||
44 | * @param int $AccountStatus |
||
45 | */ |
||
46 | View Code Duplication | public function __construct($ConfirmationNo, $Name, \DateTime $CreationDate, \DateTime $ArrivalDate, \DateTime $DepartureDate, $AccountStatus) |
|
0 ignored issues
–
show
|
|||
47 | { |
||
48 | $this->ConfirmationNo = $ConfirmationNo; |
||
49 | $this->Name = $Name; |
||
50 | $this->CreationDate = $CreationDate->format(\DateTime::ATOM); |
||
0 ignored issues
–
show
It seems like
$CreationDate->format(\DateTime::ATOM) of type string is incompatible with the declared type object<DateTime> of property $CreationDate .
Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property. Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property.. ![]() |
|||
51 | $this->ArrivalDate = $ArrivalDate->format(\DateTime::ATOM); |
||
0 ignored issues
–
show
It seems like
$ArrivalDate->format(\DateTime::ATOM) of type string is incompatible with the declared type object<DateTime> of property $ArrivalDate .
Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property. Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property.. ![]() |
|||
52 | $this->DepartureDate = $DepartureDate->format(\DateTime::ATOM); |
||
0 ignored issues
–
show
It seems like
$DepartureDate->format(\DateTime::ATOM) of type string is incompatible with the declared type object<DateTime> of property $DepartureDate .
Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property. Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property.. ![]() |
|||
53 | $this->AccountStatus = $AccountStatus; |
||
54 | } |
||
55 | |||
56 | /** |
||
57 | * @return int |
||
58 | */ |
||
59 | public function getConfirmationNo() |
||
60 | { |
||
61 | return $this->ConfirmationNo; |
||
62 | } |
||
63 | |||
64 | /** |
||
65 | * @param int $ConfirmationNo |
||
66 | * @return \Gueststream\PMS\IQWare\API\Reservations |
||
67 | */ |
||
68 | public function setConfirmationNo($ConfirmationNo) |
||
69 | { |
||
70 | $this->ConfirmationNo = $ConfirmationNo; |
||
71 | return $this; |
||
72 | } |
||
73 | |||
74 | /** |
||
75 | * @return string |
||
76 | */ |
||
77 | public function getName() |
||
78 | { |
||
79 | return $this->Name; |
||
80 | } |
||
81 | |||
82 | /** |
||
83 | * @param string $Name |
||
84 | * @return \Gueststream\PMS\IQWare\API\Reservations |
||
85 | */ |
||
86 | public function setName($Name) |
||
87 | { |
||
88 | $this->Name = $Name; |
||
89 | return $this; |
||
90 | } |
||
91 | |||
92 | /** |
||
93 | * @return \DateTime |
||
94 | */ |
||
95 | public function getCreationDate() |
||
96 | { |
||
97 | if ($this->CreationDate == null) { |
||
98 | return null; |
||
99 | } else { |
||
100 | try { |
||
101 | return new \DateTime($this->CreationDate); |
||
102 | } catch (\Exception $e) { |
||
103 | return false; |
||
104 | } |
||
105 | } |
||
106 | } |
||
107 | |||
108 | /** |
||
109 | * @param \DateTime $CreationDate |
||
110 | * @return \Gueststream\PMS\IQWare\API\Reservations |
||
111 | */ |
||
112 | public function setCreationDate(\DateTime $CreationDate) |
||
113 | { |
||
114 | $this->CreationDate = $CreationDate->format(\DateTime::ATOM); |
||
0 ignored issues
–
show
It seems like
$CreationDate->format(\DateTime::ATOM) of type string is incompatible with the declared type object<DateTime> of property $CreationDate .
Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property. Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property.. ![]() |
|||
115 | return $this; |
||
116 | } |
||
117 | |||
118 | /** |
||
119 | * @return \DateTime |
||
120 | */ |
||
121 | public function getArrivalDate() |
||
122 | { |
||
123 | if ($this->ArrivalDate == null) { |
||
124 | return null; |
||
125 | } else { |
||
126 | try { |
||
127 | return new \DateTime($this->ArrivalDate); |
||
128 | } catch (\Exception $e) { |
||
129 | return false; |
||
130 | } |
||
131 | } |
||
132 | } |
||
133 | |||
134 | /** |
||
135 | * @param \DateTime $ArrivalDate |
||
136 | * @return \Gueststream\PMS\IQWare\API\Reservations |
||
137 | */ |
||
138 | public function setArrivalDate(\DateTime $ArrivalDate) |
||
139 | { |
||
140 | $this->ArrivalDate = $ArrivalDate->format(\DateTime::ATOM); |
||
0 ignored issues
–
show
It seems like
$ArrivalDate->format(\DateTime::ATOM) of type string is incompatible with the declared type object<DateTime> of property $ArrivalDate .
Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property. Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property.. ![]() |
|||
141 | return $this; |
||
142 | } |
||
143 | |||
144 | /** |
||
145 | * @return \DateTime |
||
146 | */ |
||
147 | public function getDepartureDate() |
||
148 | { |
||
149 | if ($this->DepartureDate == null) { |
||
150 | return null; |
||
151 | } else { |
||
152 | try { |
||
153 | return new \DateTime($this->DepartureDate); |
||
154 | } catch (\Exception $e) { |
||
155 | return false; |
||
156 | } |
||
157 | } |
||
158 | } |
||
159 | |||
160 | /** |
||
161 | * @param \DateTime $DepartureDate |
||
162 | * @return \Gueststream\PMS\IQWare\API\Reservations |
||
163 | */ |
||
164 | public function setDepartureDate(\DateTime $DepartureDate) |
||
165 | { |
||
166 | $this->DepartureDate = $DepartureDate->format(\DateTime::ATOM); |
||
0 ignored issues
–
show
It seems like
$DepartureDate->format(\DateTime::ATOM) of type string is incompatible with the declared type object<DateTime> of property $DepartureDate .
Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property. Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property.. ![]() |
|||
167 | return $this; |
||
168 | } |
||
169 | |||
170 | /** |
||
171 | * @return int |
||
172 | */ |
||
173 | public function getAccountStatus() |
||
174 | { |
||
175 | return $this->AccountStatus; |
||
176 | } |
||
177 | |||
178 | /** |
||
179 | * @param int $AccountStatus |
||
180 | * @return \Gueststream\PMS\IQWare\API\Reservations |
||
181 | */ |
||
182 | public function setAccountStatus($AccountStatus) |
||
183 | { |
||
184 | $this->AccountStatus = $AccountStatus; |
||
185 | return $this; |
||
186 | } |
||
187 | } |
||
188 |
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.