Failed Conditions
Pull Request — master (#4)
by Mickael
01:17
created

AbstractSearcher

Complexity

Total Complexity 0

Size/Duplication

Total Lines 4
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 0

Importance

Changes 0
Metric Value
wmc 0
lcom 0
cbo 0
dl 0
loc 4
c 0
b 0
f 0

1 Method

Rating   Name   Duplication   Size   Complexity  
vendorName() 0 1 ?
1
<?php
2
3
/**
4
 * Author: mickael Louzet @micklouzet
5
 * File: AbstractSearcher.php
6
 * Created: 05/12/2019
7
 */
8
9
declare(strict_types=1);
10
11
namespace Louzet\ComposerLockFileParser;
12
13
abstract class AbstractSearcher {
14
15
    abstract public function vendorName(string $vendorName = '');
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...
16
}
17