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

Lock alias is not working #1150

Closed
pierredup opened this issue Nov 21, 2022 · 2 comments
Closed

Lock alias is not working #1150

pierredup opened this issue Nov 21, 2022 · 2 comments

Comments

@pierredup
Copy link
Contributor

The lock alias already exists in the recipe (#1146 (comment))

"lock": "symfony/lock",

But it's not working when trying to install the lock component.

Screenshot 2022-11-21 at 13 05 17

@pierredup
Copy link
Contributor Author

This should be resolved in symfony/flex#960

@fabpot
Copy link
Member

fabpot commented Nov 21, 2022

Let's close it here then.

@fabpot fabpot closed this as completed Nov 21, 2022
fabpot added a commit to symfony/flex that referenced this issue Nov 22, 2022
This PR was merged into the 1.x branch.

Discussion
----------

Correctly resolve the lock alias

`composer require lock` doesn't resolve the `lock` alias because the package name resolution is skipped when the package argument is `lock`. This PR bypasses this specifically for the `require` command, so that `composer require lock` correctly resolved the alias, but `composer update lock` still skips the name resolution.

Reference: symfony/recipes#1150

Commits
-------

de71648 Correctly resolve the lock alias
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

2 participants