Closed wmertens closed 7 years ago
The failing tests are due to it ignoring conditions the tests test :) No time to amend the tests right now though, sorry.
Hi @wmertens, thanks for your contribution! It makes sense but you need to fix the current failing test, which shouldn't be too hard I think, and also, can you please provide a test for that special case you've added?
Thanks! 😊
@adriantoine done :)
Tests are still not passing due to an eslint error, can you add an eslint
ignore there? Thanks!
@@ master #35 diff @@
==========================================
Files 1 1
Lines 87 89 +2
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 82 84 +2
Misses 5 5
Partials 0 0
Powered by Codecov. Last update 5fb7939...eb931a3
Hmm odd, the coverage is saying that the return;
is not being tested, but isn't that exactly what the added test does? Any ideas?
Hi @wmertens, sorry I was busy, I'm having a look now
@wmertens I think there's a typo, your config file is called empty-object.js
but in the test you're loading empty-object.config.js
, I suggest you rename empty-object.js
to empty-object.config.js
.
Good catch! I updated it.
Cool, thanks! It seems to have fixed the PR validation, not sure why we have several AppVeyor ones 🤔
@wmertens Your fix is included in v2.1.2
, thanks for your contribution! 🎉
My webpack config imports a few things and that seems to trigger the self-loading weirdness; with this patch everything works.