Introduced NoConfigResolverParametersInConstructorRule
PHPStan custom rule
#1
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.
Description:
Introduced our first custom rule to PHPStan. It guards referring to config resolver parameters in constructor (usage of methods:
hasParameter
andgetParameter
).Note: I decided to make it
nonIgnorable
which means it cannot be put into baseline. To me it is should be enforced rather than suggested as SiteAccess scope change might corrupt the actual outcome.composer phpstan
will produce the following:Moreover I provided PHPUnit coverage aligned with recommendations, ref: https://phpstan.org/developing-extensions/testing#custom-rules.
For QA:
Documentation: