Closed fredden closed 8 months ago
I've added a couple of tests to cover the "default argument value" part of this change. The other changes are only visible with the phar. What's the best way to add tests for that?
The other changes are only visible with the phar.
That's because the relative path is broken, right? Any way we can convince the suite of a changed CWD? :thinking:
I've opened #515 to get some test coverage of the phar file. When that lands, I'll update this pull request to include a check for the phar bug we're fixing here.
@fredden I see this being regularly rebased, but staying red: what are you planning for it, specifically? 🤔
I get notifications when there are merge conflicts, which I then resolve. After #512 has landed, I expect the tests here to pass. As far as I know, the changes here are good, but the test suite is currently incompatible, which is why #512 is open.
(For #512, I am currently spinning up a Windows virtual machine so I can resolve the test failures over there.)
But then I see #512 also red? :D
But then I see https://github.com/maglnet/ComposerRequireChecker/pull/512 also red
For now, yes. As mentioned, I'm working on getting a copy of Windows so I can make that green.
Thanks, that's the context I was missing! :muscle:
There are two main changes in this pull request:
--config-file
argument must exist. Previously when the argument was the same as the default, then missing files would be silently ignored. This fixes #507.