Deptrac has support for different output formatters with various options.
You can get a list of available formatters by running
$ php deptrac.php analyse --helpThe Baseline formatter is a console formatter, which generates
the skip_violations section to the given File. With this formatter it's
possible to start on a project with some violations without a failing CI Build.
Note: It's not the best solution to ignore all the errors because maybe your current Architecture doesn't allow a change without a new violation.
It can be activated with --formatter=baseline.
Supported options:
--output[=BASELINE-DUMP] path to a dumped baseline file [default: "./deptrac.baseline.yaml"]
Don't forget to include the baseline into your existing deptrac.yaml
# deptrac.yaml
imports:
- deptrac.baseline.yamlThis formatter dumps basic information to STDOUT,
examples\MyNamespace\Repository\SomeRepository::5 must not depend on examples\MyNamespace\Controllers\SomeController (Repository on Controller)
The GithubActions formatter is a console formatter, which dumps basic information
in github-actions format to STDOUT. This formatter is enabled by default while
running in a GitHub actions environment. It can be activated manually
with --formatter=github-actions.
::error file=/home/testuser/originalA.php,line=12::ACME\OriginalA must not depend on ACME\OriginalB (LayerA on LayerB)
There is a whole family of Graphviz formatters for you to choose from depending on what type of output you are expecting. They can be activated with:
--formatter=graphviz-display Automatically tries to open the image
--formatter=graphviz-dot Saves the output to a .dot file
--formatter=graphviz-html Saves the output to a .html file
--formatter=graphviz-image Saves the output to a supported image file format such as png, svg or jpg
Supported options:
--output= path to a dumped file
Under formatters.graphviz.hidden_layers you can define a list of layers you
do not want to include when using the corresponding graphviz output formatter.
The generated image will not contain these layers, but they will be part of the
analysis.
There are 2 main use-cases for this feature:
- Hiding a generic/general domains like the
vendorfolder - Having multiple "views" for your architecture. You can define a shared file
with all your
layersand arulesetand then have multiple config files for the differenthidden_layers. Using thegraphvizformatter with these files will then generate graphs focusing on only the relevant layers.
deptrac:
layers:
-
name: Utils
collectors:
-
type: classLike
value: .*Util.*
-
name: Controller
collectors:
-
type: classLike
value: .*Controller.*
ruleset:
Controller:
- Utils
formatters:
graphviz:
hidden_layers:
- UtilsAnother supported option is formatters.graphviz.groups. There you can sort
layers into groups that will be rendered as sub-graphs in GraphViz output.
The following config:
deptrac:
layers:
- User Frontend
- User Backend
- Admin Frontend
- Admin Backend
formatters:
graphviz:
groups:
User:
- User Frontend
- User Backend
Admin:
- Admin Frontend
- Admin BackendWill produce the following graph:
With formatters.graphviz.pointToGroups set to true, when you have a node inside a groups with the same name as the group itself, edges pointing to that node will point to the group instead. This might be useful for example if you want to provide a "public API" for a module defined by a group.
The MermaidJS formatter is a console formatter, which generates a mermaid.js compatible graph definition. It can be activated with --formatter=mermaidjs.
With the -o option you can specify the output file.
Available options:
--formatter=mermaidjs
--output= path to a dumped file
With this example Yaml Config:
deptrac:
layers:
- User Frontend
- User Backend
- Admin Frontend
- Admin Backend
formatters:
mermaidjs:
direction: TD
groups:
User:
- User Frontend
- User Backend
Admin:
- Admin Frontend
- Admin BackendThis will produce the following graph:
flowchart TD;
subgraph ContractGroup;
Contract;
end;
subgraph SupportiveGroup;
Supportive;
File;
end;
subgraph SymfonyGroup;
Console;
DependencyInjection;
OutputFormatter;
end;
subgraph CoreGroup;
Analyser;
Ast;
Dependency;
InputCollector;
Layer;
end;
Contract -->|6| Symfony;
InputCollector -->|3| File;
InputCollector -->|7| Symfony;
Dependency -->|36| Ast;
Layer -->|68| Ast;
Layer -->|8| Symfony;
Analyser -->|18| Ast;
Analyser -->|23| Dependency;
Analyser -->|6| Layer;
Analyser -->|10| Symfony;
Ast -->|3| Symfony;
Ast -->|3| InputCollector;
Ast -->|7| File;
OutputFormatter -->|5| Symfony;
OutputFormatter -->|1| DependencyInjection;
File -->|9| Symfony;
DependencyInjection -->|37| Symfony;
Console -->|66| Symfony;
Console -->|2| DependencyInjection;
Console -->|16| Analyser;
Console -->|5| File;
Console -->|4| OutputFormatter;
Console -->|4| Time;
By default, Json formatter dumps information to STDOUT. It can be activated
with --formatter=json
{
"Report": {
"Violations": 1,
"Skipped violations": 2,
"Uncovered": 1,
"Allowed": 0,
"Warnings": 0,
"Errors": 0
},
"files": {
"src/ClassA.php": {
"violations": 2,
"messages": [
{
"message": "ClassA must not depend on ClassB (LayerA on LayerB)",
"line": 12,
"type": "error"
},
{
"message": "ClassA should not depend on ClassC (LayerA on LayerB)",
"line": 15,
"type": "warning"
}
]
},
"src/ClassC.php": {
"violations": 1,
"messages": [
{
"message": "ClassC should not depend on ClassD (LayerA on LayerB)",
"line": 10,
"type": "warning"
}
]
},
"src/OriginalA.php": {
"violations": 1,
"messages": [
{
"message": "OriginalA has uncovered dependency on OriginalB (LayerA)",
"line": 5,
"type": "warning"
}
]
}
}
}Supported options:
--output= path to a dumped json file
The JUnit formatter dumps a JUnit Report XML file, which is quite handy in CI
environments. It is disabled by default, to activate the formatter just
use --formatter=junit.
<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
<testsuite id="1"
package=""
name="Controller"
timestamp="2018-06-07T10:09:34+00:00"
hostname="localhost"
tests="3"
failures="2"
errors="0"
time="0">
<testcase name="Controller-examples\Layer1\AnotherClassLikeAController"
classname="examples\Layer1\AnotherClassLikeAController"
time="0">
<failure message="examples\Layer1\AnotherClassLikeAController:5 must not depend on examples\Layer2\SomeOtherClass (Controller on Layer2)"
type="WARNING" />
<failure message="examples\Layer1\AnotherClassLikeAController:23 must not depend on examples\Layer2\SomeOtherClass (Controller on Layer2)"
type="WARNING" />
</testcase>
</testsuite>
<testsuite id="2"
package=""
name="Layer2"
timestamp="2018-06-07T10:09:34+00:00"
hostname="localhost"
tests="3"
failures="4"
errors="0"
time="0">
<testcase name="Layer2-examples\Layer2\SomeOtherClass2"
classname="examples\Layer2\SomeOtherClass2"
time="0">
<failure message="examples\Layer2\SomeOtherClass2:5 must not depend on examples\Layer1\SomeClass2 (Layer2 on Layer1)"
type="WARNING" />
<failure message="examples\Layer2\SomeOtherClass2:17 must not depend on examples\Layer1\SomeClass2 (Layer2 on Layer1)"
type="WARNING" />
</testcase>
<testcase name="Layer2-examples\Layer2\SomeOtherClass"
classname="examples\Layer2\SomeOtherClass"
time="0">
<failure message="examples\Layer2\SomeOtherClass:5 must not depend on examples\Layer1\SomeClass (Layer2 on Layer1)"
type="WARNING" />
<failure message="examples\Layer2\SomeOtherClass:17 must not depend on examples\Layer1\SomeClass (Layer2 on Layer1)"
type="WARNING" />
</testcase>
</testsuite>
</testsuites>Supported options:
--output= path to a dumped xml file [default: "./junit-report.xml"]
The default formatter is the table formatter, which groups results by layers to its own table. It can be also
activated with --formatter=table.
By default, Codeclimate formatter dumps information to STDOUT. It can be activated
with --formatter=codeclimate
This formatter is compatible with GitLab CI.
Supported options:
--output= path to a dumped file
Under formatters.codeclimate.severity you can define which severity string you want to assign to a given violation type. By default, deptrac uses major for failures, minor for skipped violations and info for uncovered dependencies.
deptrac:
formatters:
codeclimate:
severity:
failure: blocker
skipped: minor
uncovered: info[
{
"type": "issue",
"check_name": "Dependency violation",
"fingerprint": "3c6b66029bacb18446b7889430ec5aad7fae01cb",
"description": "ClassA must not depend on ClassB (LayerA on LayerB)",
"categories": ["Style", "Complexity"],
"severity": "major",
"location": {
"path": "ClassA.php",
"lines": {
"begin": 12
}
}
}
]