ci: fix mago install script #2730
azjezzAnnotations
11 warnings and 10 notices
|
coding standards
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
coding standards:
src/Psl/Dict/filter_keys.php#L47
Parameter `$k` is missing a type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a type hint to parameter `$k`.
|
|
coding standards:
src/Psl/Async/sleep.php#L16
Arrow function is missing a return type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a return type hint to the arrow function.
|
|
coding standards:
tests/unit/Dict/PartitionWithKeyTest.php#L37
Parameter `$_k` is missing a type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a type hint to parameter `$_k`.
|
|
coding standards:
tests/unit/Dict/PartitionWithKeyTest.php#L37
Parameter `$_v` is missing a type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a type hint to parameter `$_v`.
|
|
coding standards:
tests/unit/Dict/PartitionWithKeyTest.php#L27
Arrow function is missing a return type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a return type hint to the arrow function.
|
|
coding standards:
tests/unit/Dict/PartitionWithKeyTest.php#L32
Arrow function is missing a return type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a return type hint to the arrow function.
|
|
coding standards:
tests/unit/Dict/PartitionWithKeyTest.php#L37
Arrow function is missing a return type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a return type hint to the arrow function.
|
|
coding standards:
tests/unit/Dict/PartitionWithKeyTest.php#L42
Arrow function is missing a return type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a return type hint to the arrow function.
|
|
coding standards:
tests/unit/Dict/PartitionWithKeyTest.php#L47
Arrow function is missing a return type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a return type hint to the arrow function.
|
|
coding standards:
tests/unit/Dict/PartitionWithKeyTest.php#L52
Arrow function is missing a return type hint.
Type hints improve code readability and help prevent type-related errors.
Help: Consider adding a return type hint to the arrow function.
|
|
coding standards:
tests/static-analysis/Type/converted.php#L14
Function name `testsPurity` should be in snake case.
The function name `testsPurity` does not follow snake naming convention.
Help: Consider renaming it to `tests_purity` to adhere to the naming convention.
|
|
coding standards:
src/Psl/Comparison/Comparable.php#L12
interface name `Comparable` should be suffixed with `Interface`.
The interface name `Comparable` does not follow PSR naming convention.
Help: Consider renaming it to `ComparableInterface` to adhere to the naming convention.
|
|
coding standards:
src/Psl/Type/Exception/Exception.php#L10
Abstract class name `Exception` should be prefixed with `Abstract`.
The abstract class name `Exception` does not follow PSR naming convention.
Help: Consider renaming it to `AbstractException` to adhere to the naming convention.
|
|
coding standards:
src/Psl/Comparison/Equable.php#L10
interface name `Equable` should be suffixed with `Interface`.
The interface name `Equable` does not follow PSR naming convention.
Help: Consider renaming it to `EquableInterface` to adhere to the naming convention.
|
|
coding standards:
tests/unit/Range/FromRangeTest.php#L99
Loop body is empty
Help: Consider removing this loop or adding meaningful logic to its body.
|
|
coding standards:
tests/unit/Type/TypeTest.php#L18
Abstract class name `TypeTest` should be prefixed with `Abstract`.
The abstract class name `TypeTest` does not follow PSR naming convention.
Help: Consider renaming it to `AbstractTypeTest` to adhere to the naming convention.
|
|
coding standards:
src/Psl/Encoding/Base64/Internal/Base64.php#L25
Abstract class name `Base64` should be prefixed with `Abstract`.
The abstract class name `Base64` does not follow PSR naming convention.
Help: Consider renaming it to `AbstractBase64` to adhere to the naming convention.
|
|
coding standards:
tests/benchmark/Type/GenericTypeBench.php#L13
Abstract class name `GenericTypeBench` should be prefixed with `Abstract`.
The abstract class name `GenericTypeBench` does not follow PSR naming convention.
Help: Consider renaming it to `AbstractGenericTypeBench` to adhere to the naming convention.
|
|
coding standards:
tests/unit/Math/FloatAsserts.php#L10
Trait name `FloatAsserts` should be suffixed with `Trait`.
The trait name `FloatAsserts` does not follow PSR naming convention.
Help: Consider renaming it to `FloatAssertsTrait` to adhere to the naming convention.
|
|
coding standards:
src/Psl/Type/Type.php#L14
Abstract class name `Type` should be prefixed with `Abstract`.
The abstract class name `Type` does not follow PSR naming convention.
Help: Consider renaming it to `AbstractType` to adhere to the naming convention.
|