These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | declare(strict_types=1); |
||
4 | |||
5 | /* |
||
6 | * The MIT License (MIT) |
||
7 | * |
||
8 | * Copyright (c) 2014-2018 Spomky-Labs |
||
9 | * |
||
10 | * This software may be modified and distributed under the terms |
||
11 | * of the MIT license. See the LICENSE file for details. |
||
12 | */ |
||
13 | |||
14 | namespace OAuth2Framework\Component\Core\User; |
||
15 | |||
16 | use OAuth2Framework\Component\Core\UserAccount\UserAccountId; |
||
17 | |||
18 | interface User |
||
19 | { |
||
20 | public function getLastLoginAt(): ?int; |
||
0 ignored issues
–
show
|
|||
21 | |||
22 | public function getLastUpdateAt(): ?int; |
||
0 ignored issues
–
show
For interfaces and abstract methods it is generally a good practice to add a
@return annotation even if it is just @return void or @return null , so that implementors know what to do in the overridden method.
For interface and abstract methods, it is impossible to infer the return type
from the immediate code. In these cases, it is generally advisible to explicitly
annotate these methods with a
Loading history...
|
|||
23 | |||
24 | /** |
||
25 | * @return string[] |
||
26 | */ |
||
27 | public function getAccountIds(UserAccountId $userAccountId): array; |
||
28 | |||
29 | public function hasAccountId(UserAccountId $userAccountId): bool; |
||
30 | } |
||
31 |
For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a
@return
doc comment to communicate to implementors of these methods what they are expected to return.