Add ignore_parse_errors option to ComposerRequireChecker #460
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.
This adds an option to enable
--ignore-parse-errors
, which is available in ComposerRequireChecker since 0.2.0.One thing to note is that
the world will crash and burnComposerRequireChecker will throw a hissy fit if you have <0.2.0 installed and enable this. I think pointing this out in the docs should be good enough since the option is opt-in. We could always go down the route of version detection, butcomposer-require-checker --version
identifies itself as0.1.1-dev
on 0.2.0 :(