You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proposal here is to add this feature directly into Composer, allowing custom completion where appropriate, for example
composer require sa<TAB> could search Packagist for packages with name sa%
composer update <TAB> could complete package names already in composer.json
etc.
The completion script could then be generated and shipped when Composer is distributed as a native package (for example, I'm using a package prepared by Remi), meaning many users will get DX improvement by default, others can run composer completion bash > ~/.bash_completion.d/composer.sh (or similar) once to get the same features.
The text was updated successfully, but these errors were encountered:
According to this tweet:
https://twitter.com/seldaek/status/1461670175976169478
Composer 2.3+ will be on Symfony 5.4 which got support for completion in Console. See Symfony 5.4 adding completion to their own commands.
The proposal here is to add this feature directly into Composer, allowing custom completion where appropriate, for example
composer require sa<TAB>
could search Packagist for packages with namesa%
composer update <TAB>
could complete package names already incomposer.json
etc.
The completion script could then be generated and shipped when Composer is distributed as a native package (for example, I'm using a package prepared by Remi), meaning many users will get DX improvement by default, others can run
composer completion bash > ~/.bash_completion.d/composer.sh
(or similar) once to get the same features.The text was updated successfully, but these errors were encountered: