Test Setup Failed
Pull Request — master (#39)
by Pierre
12:34
created

FixturesFactory

Size/Duplication

Total Lines 11
Duplicated Lines 0 %

Importance

Changes 0
Metric Value
dl 0
loc 11
c 0
b 0
f 0

3 Methods

Rating   Name   Duplication   Size   Complexity  
addProcessor() 0 1 ?
addProvider() 0 1 ?
create() 0 1 ?
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
Documentation introduced by
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...
14
15
    /**
16
     * @param object $provider
17
     */
18
    public function addProvider($provider);
0 ignored issues
show
Documentation introduced by
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...
19
20
    public function create(ObjectManager $om, string $locale = null): Fixtures;
21
}
22