These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | declare(strict_types=1); |
||
4 | |||
5 | namespace Knp\Rad\FixturesLoad; |
||
6 | |||
7 | use Doctrine\Common\Persistence\ObjectManager; |
||
8 | use Nelmio\Alice\Fixtures; |
||
9 | use Nelmio\Alice\ProcessorInterface; |
||
10 | |||
11 | interface FixturesFactory |
||
12 | { |
||
13 | public function addProcessor(ProcessorInterface $processor); |
||
0 ignored issues
–
show
|
|||
14 | |||
15 | /** |
||
16 | * @param object $provider |
||
17 | */ |
||
18 | public function addProvider($provider); |
||
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...
|
|||
19 | |||
20 | public function create(ObjectManager $om, string $locale = null): Fixtures; |
||
21 | } |
||
22 |
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.