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 Kunstmaan\FixturesBundle\Populator\Methods; |
||
4 | |||
5 | interface MethodInterface |
||
6 | { |
||
7 | /** |
||
8 | * returns true if the method is able to set the property to the value on the object described by the given fixture |
||
9 | * |
||
10 | * @param mixed $object |
||
11 | * @param string $property |
||
12 | * @param mixed $value |
||
13 | */ |
||
14 | public function canSet($object, $property, $value); |
||
0 ignored issues
–
show
|
|||
15 | |||
16 | /** |
||
17 | * @param mixed $object |
||
18 | * @param string $property |
||
19 | * @param mixed $value |
||
20 | */ |
||
21 | public function set($object, $property, $value); |
||
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 ![]() |
|||
22 | } |
||
23 |
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.