The type Sonata\AdminBundle\Tests\Fixtures\StubTranslator has been defined more than once; this definition is ignored, only the first definition in this file (L20-26) is considered.
This check looks for classes that have been defined more than once in the same file.
If you can, we would recommend to use standard object-oriented programming
techniques. For example, to avoid multiple types, it might make sense to create a
common interface, and then multiple, different implementations for that interface.
This also has the side-effect of providing you with better IDE auto-completion,
static analysis and also better OPCode caching from PHP.
The interface Symfony\Component\Translation\TranslatorInterface has been deprecated with message: since Symfony 4.2, use Symfony\Contracts\Translation\TranslatorInterface instead
This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message.
The explanatory message should give you some clue as to whether and when the type will be
removed from the class and what other constant to use instead.
Loading history...
29
{
30
public function trans($id, array $parameters = [], $domain = null, $locale = null)
31
{
32
return '[trans]'.$id.'[/trans]';
33
}
34
35
public function transChoice($id, $number, array $parameters = [], $domain = null, $locale = null)
sonata-project /
SonataAdminBundle
Loading history...
This check looks for classes that have been defined more than once in the same file.
If you can, we would recommend to use standard object-oriented programming techniques. For example, to avoid multiple types, it might make sense to create a common interface, and then multiple, different implementations for that interface.
This also has the side-effect of providing you with better IDE auto-completion, static analysis and also better OPCode caching from PHP.