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
It doesn't make much sense to arbitrary include "xt/{author,release}/*" in the "tests use" part, because those tests are not run during install, and are only run during development.
Further digging suggests that this was added in version 0.75, but however, the rationale doesn't really make complete sense as xt/ is not automatically used by any of the standard tool-chains
Even then, only "xt/smoke/*" makes any degree of sense to scan for build/test deps.
As per cpants/www-cpants#11 ,
It doesn't make much sense to arbitrary include "xt/{author,release}/*" in the "tests use" part, because those tests are not run during install, and are only run during development.
Further digging suggests that this was added in version 0.75, but however, the rationale doesn't really make complete sense as xt/ is not automatically used by any of the standard tool-chains
Even then, only "xt/smoke/*" makes any degree of sense to scan for build/test deps.
https://metacpan.org/diff/release/DOMM/Module-CPANTS-Analyse-v0.74/DOMM/Module-CPANTS-Analyse-0.75
The text was updated successfully, but these errors were encountered: