Feature - Reformatting for linting, format and analysis with Mago - #173
Closed
simon-mundy wants to merge 2 commits into
Closed
Feature - Reformatting for linting, format and analysis with Mago#173simon-mundy wants to merge 2 commits into
simon-mundy wants to merge 2 commits into
Annotations
2 errors, 5 warnings, and 1 notice
|
Lint
Process completed with exit code 1.
|
|
Lint:
src/TableGateway/Feature/RowGatewayFeature.php#L16
Class has high complexity.
>Class has a cyclomatic complexity of 16, which exceeds the threshold of 15.
|
|
Analyze:
src/TableGateway/Feature/SequenceFeature.php#L130
Assigning `mixed` type to a variable may lead to unexpected behavior.
>This expression has type `mixed`.
>Assigning `mixed` type here.
Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type.
Help: Consider using a more specific type to avoid potential issues.
|
|
Analyze:
src/TableGateway/Feature/MetadataFeature.php#L68
Assigning `nonnull` type to a variable may lead to unexpected behavior.
>This expression has type `nonnull`.
>Assigning `nonnull` type here.
Using `nonnull` can lead to runtime errors if the variable is used in a way that assumes a specific type.
Help: Consider using a more specific type to avoid potential issues.
|
|
Analyze:
src/TableGateway/Feature/MetadataFeature.php#L46
Assigning `mixed` type to a variable may lead to unexpected behavior.
>Assigning `mixed` type here.
Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type.
Help: Consider using a more specific type to avoid potential issues.
|
|
Analyze:
src/TableGateway/Feature/RowGatewayFeature.php#L38
Assigning `mixed` type to a variable may lead to unexpected behavior.
>This expression has type `mixed`.
>Assigning `mixed` type here.
Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type.
Help: Consider using a more specific type to avoid potential issues.
|
|
Lint:
src/TableGateway/Feature/SequenceFeature.php#L45
TODO should be tagged with (@username) or (#issue).
>TODO comment is untagged
Help: Add a user tag or issue reference to the TODO comment, e.g. TODO(@azjezz), TODO(azjezz), TODO(#123).
|
|
Analyze:
src/RowGateway/Feature/FeatureSet.php#L24
Property `$magicSpecifications` is never used.
>Property `$magicSpecifications` is declared here.
This property is declared but never read or written within the class.
Help: Consider prefixing the property with an underscore (`$_`) to indicate that it is intentionally unused, or remove it if it is not needed.
|
background
wait
wait-all
cancel
parallel
Loading