Bump wildcard constraint #11694
Merged
Bump wildcard constraint #11694
Conversation
This file contains 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
|
Hm interesting.. I kinda hate it but also it makes sense strictly speaking. So thanks? ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I recently ran
composer bumpon a project which used a wildcard constraint (*) for a particular package.The help text for the
bumpcommand reads:However the lower-limit for the wildcard constraint (
*) was not changed. This pull request adds this functionality.While I do not believe that unbound version constraints should be used generally, I recognise that others have different opinions and that there are valid use-cases for such constraints.