Skip to content

Applying design pattern practices to a better code comprehension #34

Applying design pattern practices to a better code comprehension

Applying design pattern practices to a better code comprehension #34

Triggered via pull request April 15, 2024 13:52
@htrgouveahtrgouvea
synchronize #46
develop
Status Failure
Total duration 18s
Artifacts

linter.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

9 errors
critic: lib/Zarn/AST.pm#L46
Code structure is deeply nested at line 46, column 29. Consider refactoring.
critic: lib/Zarn/AST.pm#L49
Code structure is deeply nested at line 49, column 33. Consider refactoring.
critic: lib/Zarn/AST.pm#L57
Code structure is deeply nested at line 57, column 33. Consider refactoring.
critic: lib/Zarn/Engine/AST.pm#L12
"$rules" is declared but not used at line 12, column 9. Unused variables clutter code and make it harder to read.
critic: lib/Zarn/Engine/AST.pm#L12
"@results" is declared but not used at line 12, column 9. Unused variables clutter code and make it harder to read.
critic: lib/Zarn/Engine/Source_to_Sink.pm#L39
Code structure is deeply nested at line 39, column 29. Consider refactoring.
critic: tools/view-ast.pl#L9
Subroutine "main" does not end with "return" at line 9, column 1. See page 197 of PBP.
critic: samples/false-positive.pl#L7
Subroutine "main" does not end with "return" at line 7, column 1. See page 197 of PBP.
critic: samples/code-injection.pl#L7
Subroutine "main" does not end with "return" at line 7, column 1. See page 197 of PBP.