chore: switch to mago (#501) #2732
Annotations
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/Internal/Loader.php#L28
Class constant `CONSTANTS` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `CONSTANTS`.
|
coding standards:
src/Psl/Internal/Loader.php#L76
Class constant `FUNCTIONS` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `FUNCTIONS`.
|
coding standards:
src/Psl/Internal/Loader.php#L564
Class constant `INTERFACES` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `INTERFACES`.
|
coding standards:
src/Psl/Internal/Loader.php#L662
Class constant `TRAITS` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `TRAITS`.
|
coding standards:
src/Psl/Internal/Loader.php#L671
Class constant `CLASSES` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `CLASSES`.
|
coding standards:
src/Psl/Internal/Loader.php#L887
Class constant `ENUMS` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `ENUMS`.
|
coding standards:
src/Psl/Internal/Loader.php#L912
Class constant `TYPE_CONSTANTS` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `TYPE_CONSTANTS`.
|
coding standards:
src/Psl/Internal/Loader.php#L914
Class constant `TYPE_FUNCTION` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `TYPE_FUNCTION`.
|
coding standards:
src/Psl/Internal/Loader.php#L916
Class constant `TYPE_INTERFACE` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `TYPE_INTERFACE`.
|
coding standards:
src/Psl/Internal/Loader.php#L918
Class constant `TYPE_TRAIT` is missing a type hint.
Adding a type hint to constants improves code readability and helps prevent type errors.
Help: Consider specifying a type hint for `TYPE_TRAIT`.
|
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:
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:
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/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.
|
coding standards:
tests/static-analysis/Comparison/comparable.php#L21
Abstract class name `Size` should be prefixed with `Abstract`.
The abstract class name `Size` does not follow PSR naming convention.
Help: Consider renaming it to `AbstractSize` 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/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/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.
|