Completed
Push — 5.0 ( a48099...63af02 )
by
unknown
11:33
created

FormBundle/Entity/FormAdaptorInterface.php (1 issue)

Upgrade to new PHP Analysis Engine

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
7
use Symfony\Component\Form\FormBuilderInterface;
8
9
/**
10
 * Form adaptor Interface
11
 */
12
interface FormAdaptorInterface
13
{
14
15
    /**
16
     * Modify the given FormBuilderInterface
17
     *
18
     * @param FormBuilderInterface $formBuilder The form builder
19
     * @param ArrayObject          $fields      The fields
20
     * @param int                  $sequence    The sequence of the form field
21
     */
22
    public function adaptForm(FormBuilderInterface $formBuilder, ArrayObject $fields, $sequence);
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 @return doc comment to communicate to implementors of these methods what they are expected to return.

Loading history...
23
24
    /**
25
     * Returns a unique id
26
     *
27
     * @return string
28
     */
29
    public function getUniqueId();
30
31
}
32