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\AdminBundle\Helper\FormWidgets; |
||
4 | |||
5 | use Doctrine\ORM\EntityManager; |
||
6 | use Symfony\Component\Form\FormBuilderInterface; |
||
7 | use Symfony\Component\Form\FormView; |
||
8 | use Symfony\Component\HttpFoundation\Request; |
||
9 | |||
10 | /** |
||
11 | * A tab can be added to the TabPane and show fields or other information of a certain entity |
||
12 | */ |
||
13 | interface FormWidgetInterface |
||
14 | { |
||
15 | /** |
||
16 | * @param FormBuilderInterface $builder The form builder |
||
17 | */ |
||
18 | public function buildForm(FormBuilderInterface $builder); |
||
0 ignored issues
–
show
|
|||
19 | |||
20 | /** |
||
21 | * @param Request $request |
||
22 | */ |
||
23 | public function bindRequest(Request $request); |
||
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...
|
|||
24 | |||
25 | /** |
||
26 | * @param EntityManager $em The entity manager |
||
27 | */ |
||
28 | public function persist(EntityManager $em); |
||
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...
|
|||
29 | |||
30 | /** |
||
31 | * @param FormView $formView |
||
32 | * |
||
33 | * @return array |
||
34 | */ |
||
35 | public function getFormErrors(FormView $formView); |
||
36 | |||
37 | /** |
||
38 | * @return string |
||
39 | */ |
||
40 | public function getIdentifier(); |
||
41 | |||
42 | /** |
||
43 | * @param string $identifier |
||
44 | * |
||
45 | * @return TabInterface |
||
46 | */ |
||
47 | public function setIdentifier($identifier); |
||
48 | |||
49 | /** |
||
50 | * @return string |
||
51 | */ |
||
52 | public function getTemplate(); |
||
53 | |||
54 | /** |
||
55 | * @param Request $request |
||
56 | * |
||
57 | * @return array |
||
58 | */ |
||
59 | public function getExtraParams(Request $request); |
||
60 | } |
||
61 |
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.