-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Removal of global option "no" is gone? Currently parsing it like --yes ! #6179
Comments
Yes this changed several years ago when we adopted symfony console. -n in all console apps is short for --no-interaction which does behave similar to --yes. Use --no to get old behavior. |
Thanks for raising this and a fast answer.
... but
|
Now you are changing the intent of this issue. Feel free to discuss in #6162 |
Describe the bug
I cannot find the docs, but we used to do commands as dry-run / sanity check;
Things like
drush cim -n
(kinda like what config:status does)but now the no-shorthand is interpreted as a
YES
-- that cannot be right!Also help-section
Global options
has no mention about the "no" argument.To Reproduce
Use a command that uses a yes/no promt (eg.
drush cim
ordrush sqlsan
)See that it requires a promt
now add
-n
and see that it is interpreted likeyes
now change the
-n
into--no
and see that it is interpreted likeno
Expected behavior
-n should be the shorthand for --no (or at leased not yes)
Actual behavior
-n is now the shorthand for --yes
Or more likely the
--no-interaction
?didnt look at the code yet
Workaround
write fullout
--no
argSystem Configuration
Additional information
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: