More work on better triggers in issues #560
Annotations
10 warnings
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Unexpected error while parsing tmp/v1.13/lib/elixir/test/elixir/kernel/sigils_test.exs: [%Credo.Issue{category: :error, check: Credo.Code.ParserError, column: nil, diff_marker: nil, exit_status: 0, filename: "nofilename", line_no: [line: 107, column: 3], message: {"unexpected reserved word: ", ""}, meta: [], priority: 0, scope: nil, severity: nil, trigger: nil}]
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
|
Run mix credo tmp/v1.13 --strict --mute-exit-status
Nested modules could be aliased at the top of the invoking module.
|
The logs for this run have expired and are no longer available.
Loading