Repository navigation
chore: harness 0.1.6, and the dependency analysis blocks - #25
Merged
Merged
Conversation
The dependency analysis passes with the harness preset and this package's own composer-dependency-analyser.php, each exception with its reason. Still reported only: Rector.
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
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.
Harness 0.1.6: the dependency analysis (ARCH-07) ignores WordPress classes and functions, the usual PHP extensions and the tests. What is specific to this package is in
composer-dependency-analyser.php(when it needs one), each exception with its reason. The gate passes, so it leavesobservedand now blocks. Still reported only: Rector.