This class seems to be duplicated in your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate
the same code in three or more different places, we strongly encourage you to
look into extracting the code into a single class or operation.
You can also find more detailed suggestions in the “Code” section of your repository.
Loading history...
20
{
21
/** @var Factory */
22
protected $uiFactory;
23
24
/**
25
* TextField constructor.
26
*
27
* @param Factory $uiFactory
28
*/
29
public function __construct(Factory $uiFactory)
30
{
31
$this->uiFactory = $uiFactory;
32
}
33
34
/**
35
* @inheritdoc
36
*/
37
public function build(ConfigInterface $config, $width, ManialinkInterface $manialink, ManialinkFactory $manialinkFactory): Renderable
The class eXpansion\Framework\Config\Model\PasswordConfig does not exist. Did you forget a USE statement, or did you not list all dependencies?
This error could be the result of:
1. Missing dependencies
PHP Analyzer uses your composer.json file (if available) to determine the
dependencies of your project and to determine all the available classes and functions.
It expects the composer.json to be in the root folder of your repository.
Are you sure this class is defined by one of your dependencies, or did you maybe
not list a dependency in either the require or require-dev section?
2. Missing use statement
PHP does not complain about undefined classes in ìnstanceof checks. For
example, the following PHP code will work perfectly fine:
if($xinstanceofDoesNotExist){// Do something.}
If you have not tested against this specific condition, such errors might go
unnoticed.
Loading history...
51
}
52
53
/**
54
* Get raw value to set from gui entry data.
55
*
56
* @param ConfigInterface $config
57
* @param $entry
58
*
59
* @return mixed
60
*/
61
public function getRawValueFromEntry(ConfigInterface $config, $entry)
eXpansionPluginPack /
eXpansion2
Loading history...
Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.
You can also find more detailed suggestions in the “Code” section of your repository.