-
-
Notifications
You must be signed in to change notification settings - Fork 22
Updated phpstan/phpstan to version 2.x #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,8 +4,10 @@ | |
| # vendor/bin/phpstan analyse app --memory-limit 200M -l 0 | ||
| # | ||
| includes: | ||
| - vendor/phpstan/phpstan-strict-rules/rules.neon | ||
| # 需要执行 composer require phpstan/phpstan-deprecation-rules --dev | ||
| # - vendor/phpstan/phpstan-deprecation-rules/rules.neon | ||
|
Comment on lines
6
to
9
|
||
|
|
||
| parameters: | ||
| level: 0 | ||
| paths: | ||
|
|
@@ -24,9 +26,6 @@ services: | |
| # When using `match` to match enum, the enumeration must be completely overwritten | ||
| - class: PHPStan\Rules\Comparison\MatchExpressionRule | ||
| arguments: | ||
| checkAlwaysTrueStrictComparison: %checkAlwaysTrueStrictComparison% | ||
| disableUnreachable: %featureToggles.disableUnreachableBranchesRules% | ||
| reportAlwaysTrueInLastCondition: %reportAlwaysTrueInLastCondition% | ||
| treatPhpDocTypesAsCertain: %treatPhpDocTypesAsCertain% | ||
| tags: | ||
| - phpstan.rules.rule | ||
| - phpstan.rules.rule | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR metadata/description says this change only bumps phpstan/phpstan to ^2.0, but this hunk also introduces a new dev dependency (phpstan/phpstan-strict-rules) and changes the phpstan script memory limit. Please update the PR title/description to reflect the additional scope (or split these changes into a separate PR) so reviewers/CI expectations match the actual diff.