Jordi Boggiano

Not all projects have a name, dir may be machine-dependent.. I'm not sure really if this is worth doing in a non-opt-in manner as it is now.

Yeah I can see the value, but I'm not sure how easy it would be to handle in a case like your `fix` example above, which then requires resolving scripts...

@willrowe one workaround for your use case would be to stop argument parsing for composer install by adding -- ``` "@composer install --no-dev --", ``` This trick won't work for...

Ah yes for install it doens't work because install takes arguments on top of options and `--` only stops option parsing. Then yes having an explicit {args} somewhere would help...

Thanks for getting started here. This definitely is better than nothing as it runs the code and would catch any critical error, but it'd be cool if you find time...

I believe flex should not do changes on prod as long as you deploy/commit symfony.lock as well as composer.json (is that correct understanding @nicolas-grekas ?)

@hubertnnn I'm still not sure what you are looking for? That we document the fact that the require command runs post-update-cmd scripts?

Without more details nobody will be able to help you..

If `curl` fails to connect as well it's definitely not a Composer issue, but must be something in your environment/network. It seems the TLS handshake fails entirely, so I guess...

Yes the update filtering I realize. I don't really feel like this is worth doing tho, seems like a pain to implement, even more complexity in problem output, etc. Not...