Open Kurt-von-Laven opened 1 year ago
I use jscpd a lot on my pro projects, i'll check with beta I'll downgrade devskim in another pr
I can confirm this as well.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
If you think this issue should stay open, please remove the O: stale 🤖
label or comment on the issue.
Describe the bug Starting in v6.20.0, jscpd began failing when run via MegaLinter on repositories containing at least 1 clone even if they configured a sufficiently high threshold.
To Reproduce Steps to reproduce the behavior:
.jscpd.json
so that jscpd should pass unconditionally.npx jscpd@3.5.3 .
, and observe that jscpd passes.npx jscpd@3.5.3 --exitCode 1 .
, and observe that jscpd fails.Expected behavior jscpd should succeed if and only if the percentage of duplicated lines doesn't exceed the configured threshold.
Additional context This bug was introduced by uncommenting
--exitCode 1
in #2329. I believe the solution is to delete these arguments; please let me know if anyone anticipates any drawbacks to this change.