You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, while doing some tests on a project, I figured out that somehow, when placing the flag --report-uncovered (or --fail-on-uncovered) before specifying the configuration file through the --config-file option, this last one is ignored and deptrac tries to use the default configuration file instead.
The problem doesn't occur for the --no-cache flag for instance but I've not tested the other ones.
Examples:
Running tools/vendor/bin/deptrac analyze --config-file=deptrac_hexagonal.yaml --report-uncovered will works properly, with the following output:
But running tools/vendor/bin/deptrac analyze --report-uncovered --config-file=deptrac_hexagonal.yaml will give me an error due to deptrac.yml not being found:
In CannotLoadConfiguration.php line 12:
Could not load deptrac.yaml. Reason: The file "deptrac.yaml" does not exist (in: "/var/www").
For additional information, I tested the same operation on another project where qossmic/deptrac-shim:1.0.2 is installed instead and it seems to work without any issue.
The text was updated successfully, but these errors were encountered:
Closes request #39741: qossmic/deptrac-shim: 1.0.2 -> qossmic/deptrac:
2.0.1
No functional change. CI should be happy.
Notes:
- "regex" configuration is now "value".
- I could not make the "class" collector work, defaulting to
"classLike".
- Due to a bug [0], the `--report-uncovered` and `--fail-on-uncovered`
flags MUST come after `--config-file`, or deptrac will not find the file
and raise an error that it did not find `deptrac.yaml` (the default
file).
- There are still 7 existing core -> plugins violations, but for an
unknown reason, deptrac does not see them on the CI:
PermissionsManager:
- Tuleap\Tracker\TrackerDuplicationUserGroupMapping
PermissionsDao:
- Tuleap\Tracker\TrackerDuplicationType
- Tuleap\Tracker\TrackerDuplicationUserGroupMapping
Tuleap\Reference\CrossReferenceManager:
- Tuleap\Tracker\Artifact\Artifact
- Tuleap\Tracker\Artifact\ArtifactsDeletion\DeletionContext
Tuleap\Project\UGroups\XML\XMLUserGroup
- Tuleap\Tracker\XML\XMLUser
[0] qossmic/deptrac#1425
Change-Id: Ifc5d7ea1735d56cd3909b87f3130bd7189056162
Tested on: 2.0.1
Hello, while doing some tests on a project, I figured out that somehow, when placing the flag
--report-uncovered
(or--fail-on-uncovered
) before specifying the configuration file through the--config-file
option, this last one is ignored anddeptrac
tries to use the default configuration file instead.The problem doesn't occur for the
--no-cache
flag for instance but I've not tested the other ones.Examples:
Running
tools/vendor/bin/deptrac analyze --config-file=deptrac_hexagonal.yaml --report-uncovered
will works properly, with the following output:But running
tools/vendor/bin/deptrac analyze --report-uncovered --config-file=deptrac_hexagonal.yaml
will give me an error due todeptrac.yml
not being found:For additional information, I tested the same operation on another project where
qossmic/deptrac-shim:1.0.2
is installed instead and it seems to work without any issue.The text was updated successfully, but these errors were encountered: