-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass composer parameters to update subcommand #738
Labels
Comments
1 task
Since this issue has not had any activity within the last 180 days, I have marked it as stale. I will close it if no further activity occurs within the next 14 days. |
Since this issue has not had any activity within the last 180 days, I have marked it as stale. I will close it if no further activity occurs within the next 14 days. |
Thanks! |
You are welcome, @xurizaemon! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
ANSI or no-ANSI output is relatively trivial, but I would expect
composer --foo normalize
to pass--foo
on to any Composer subcommands. Currently I believe it does not, and propose that we change this.There may be Other Considerations, I'm not strongly wedded to this change :)
We might want to include or exclude specific composer switches to retain existing behaviour (eg
--no-update-lock
behaviour should not change?).Steps required to reproduce the problem
composer --no-ansi normalize
, eg in a CI processExpected Result
Actual Result
The text was updated successfully, but these errors were encountered: