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
In doherty/Dist-Zilla-Plugin-Test-UnusedVars#5, @karenetheridge pointed out that using the static MANIFEST means that all_vars_ok doesn't test all the files. In particular, it misses any which were generated at build time. They aren't listed in the MANIFEST, because MANIFEST is about listing the files that should be included in the tarball. If you listed a file that wasn't there yet, the build tools would think their kit was incomplete.
MANIFEST isn't intended for this purpose. Instead, you should dynamically search for the files you're going to test.
Could you explain why on both counts? It seems like doing the unsurprising thing by default is a better choice. Also, I'm not sure I see the harm in the additional (common) dependencies for an author test.
In doherty/Dist-Zilla-Plugin-Test-UnusedVars#5, @karenetheridge pointed out that using the static MANIFEST means that
all_vars_ok
doesn't test all the files. In particular, it misses any which were generated at build time. They aren't listed in the MANIFEST, because MANIFEST is about listing the files that should be included in the tarball. If you listed a file that wasn't there yet, the build tools would think their kit was incomplete.MANIFEST isn't intended for this purpose. Instead, you should dynamically search for the files you're going to test.
Compare with how
Test::Compile
orTest::Version
do it.The text was updated successfully, but these errors were encountered: