We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the upcoming PHPStan 1.11 we'll see // identifier: comments. Could this be useful to further analyze the baseline?
// identifier:
phpstan/phpstan-src@4b32cac
The text was updated successfully, but these errors were encountered:
I thought about that. It will definitely have an impact on this lib and its feature set.
Some things which are currently build here will be possible natively in a similar way.
I am open for discussion
Sorry, something went wrong.
The reason why I brought it up was that I just tried this package and got this result:
Analyzing phpstan-baseline.php Date: Tue, 31 Oct 2023 08:45:30 +0000 Overall-Errors: 11957 Classes-Cognitive-Complexity: 0 Deprecations: 299 Invalid-Phpdocs: 66 Unknown-Types: 39 Anonymous-Variables: 0 Native-Property-Type-Coverage: 0 Native-Param-Type-Coverage: 0 Native-Return-Type-Coverage: 0 Unused-Symbols: 0
Not very helpful as everything is marked as Overall-Errors. 😅 I hope that error identifiers will improve this list.
Overall-Errors
it depends on the rules you use. atm we count only those errors emitted by the rules mentioned in the readme.
but I agree, we could aggregate errors by native identifiers
No branches or pull requests
In the upcoming PHPStan 1.11 we'll see
// identifier:
comments. Could this be useful to further analyze the baseline?phpstan/phpstan-src@4b32cac
The text was updated successfully, but these errors were encountered: