Add --no-check-lock option support #947
Merged
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
|
The only thing that is missing is tests - unfortunately I haven't figured out this part. |
|
Looks nice! Thanks for the addition. Just to answer your question : we transitioned the task system at some point in time. Looks like you found that during your PR, so that's nice! :) |
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.
GrumPHP 1.5.0composer-normalize introduced
--no-check-lockoption in 2.7.0 release back in August 2020.This option is very useful when you work on a library project and you only concerned about the
composer.jsonfile but not that much about the lock file that only exists in the development environment for the library itself.It would be awesome to see it available via configuration for the
composer_normalizetask.