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\FormBundle\Entity; |
||
4 | |||
5 | use ArrayObject; |
||
6 | use Symfony\Component\Form\FormBuilderInterface; |
||
7 | |||
8 | /** |
||
9 | * Form adaptor Interface |
||
10 | */ |
||
11 | interface FormAdaptorInterface |
||
12 | { |
||
13 | /** |
||
14 | * Modify the given FormBuilderInterface |
||
15 | * |
||
16 | * @param FormBuilderInterface $formBuilder The form builder |
||
17 | * @param ArrayObject $fields The fields |
||
18 | * @param int $sequence The sequence of the form field |
||
19 | */ |
||
20 | public function adaptForm(FormBuilderInterface $formBuilder, ArrayObject $fields, $sequence); |
||
0 ignored issues
–
show
|
|||
21 | |||
22 | /** |
||
23 | * Returns a unique id |
||
24 | * |
||
25 | * @return string |
||
26 | */ |
||
27 | public function getUniqueId(); |
||
28 | } |
||
29 |
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.