Completed
Push — develop ( 8eb671...133594 )
by Mike
19:30 queued 09:24
created

assets/singlefile/syntax/7.1-pseudo-types.php (3 issues)

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

1
<?php
2
class A
0 ignored issues
show
Comprehensibility Best Practice introduced by
The type A has been defined more than once; this definition is ignored, only the first definition in tests/features/assets/si...sicClassInheritance.php (L10-19) is considered.

This check looks for classes that have been defined more than once.

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.

Loading history...
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
3
{
4
    public function method(array $array): iterable
0 ignored issues
show
The parameter $array is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
5
    {
6
    }
7
}
8