Correctly resolve the lock alias#960
Merged
fabpot merged 1 commit intosymfony:1.xfrom Nov 22, 2022
Merged
Conversation
nicolas-grekas
approved these changes
Nov 21, 2022
kbond
approved these changes
Nov 21, 2022
ogizanagi
approved these changes
Nov 21, 2022
Member
|
Thank you @pierredup. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
composer require lockdoesn't resolve thelockalias because the package name resolution is skipped when the package argument islock. This PR bypasses this specifically for therequirecommand, so thatcomposer require lockcorrectly resolved the alias, butcomposer update lockstill skips the name resolution.Reference: symfony/recipes#1150