Marco Pivetta
Marco Pivetta
Btw, yes, I fully understand where this comes from: I'm just saying that the exit code with this particular tool will always be `1`. We have similar "opt-in dependencies" in...
> Plus for that case, it will an issue for a lot of people following the Symfony standard. I said it many, many, many many times: I don't care what...
I don't see `webmozart/assert` in your dependencies
`bundles.php` should most likely contain only prod info: if you have an `if (APP_ENV === 'dev') {` switch in there, you can segregate it out to your `test/` dir
Yes, and you can split the development config into a separate file to be put somewhere outside your sources.
Also: ```sh mkdir /tmp/my-tool cd /tmp/my-tool composer require ``` Good enough
Adding more gasoline to the fire: * #283 reported a bug that is due to an outdated dependency in the `.phar` * #281 reports broken `.phar` * #140 reports a...
> Reporting them ought to be fairly easy? You mean figuring out the `composer.json` in a parent directory of any of these?
Ah yes, this should be feasible, but it requires switching to https://github.com/Roave/BetterReflection first, so that files can be located without being actually loaded.
Indeed, I think reflection is not used at all in here: probably outdated reasoning.