Skip to content
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

Drush command local:import vs locale:import #4221

Open
davidferlay opened this issue Oct 16, 2019 · 2 comments
Open

Drush command local:import vs locale:import #4221

davidferlay opened this issue Oct 16, 2019 · 2 comments

Comments

@davidferlay
Copy link

davidferlay commented Oct 16, 2019

Current behavior

  • command drush locale:import exists and work just fine
  • command drush local:import exists as well but does show the sames options

2019-10-17_15-55

2019-10-17_16-00

2019-10-17_15-56

Expected behavior

  • Both drush commands should behave similar, providing that one is an alias of the other

Describe the solution you'd like

I believe it is misleading to keep both commands as they clearly don't work the same way and one seem more complete that the other.

I propose to remove drush local:import

@davidferlay davidferlay changed the title Add existing UI options to drush locale:import Drush command local:import vs locale:import Oct 17, 2019
@andypost
Copy link
Contributor

So the real issue is strange - when you type local:import it not always can find this command
Guess autosuggester used some place

@Chi-teck
Copy link
Collaborator

Chi-teck commented Oct 18, 2019

It's also possible to execute that command by typing drush l:im or drush lo:i.
That feature comes with Symfony Console, however apparently help command is not aware about command shortcuts.
https://symfony.com/doc/current/components/console/usage.html#shortcut-syntax

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants