Completed
Push — master ( 1de9b7...830752 )
by Kristof
38:46 queued 24:09
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
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
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...
21
22
    /**
23
     * Returns a unique id
24
     *
25
     * @return string
26
     */
27
    public function getUniqueId();
28
}
29