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
I saw #151 was added by @villfa to check for non static data provider. But I don't have the check on my project.
If I understand correctly, it's only active if https://github.com/phpstan/phpstan-deprecation-rules is installed. But I'd like to have this rule even if I don't use the deprecation-rules package.
Currently stricter analysis (https://phpstan.org/config-reference#stricter-analysis) with PHPStan is possible
I'd like the same for the non-static check, ie: a config option to enable this rules (which would be automatically set to true if https://github.com/phpstan/phpstan-deprecation-rules is installed).
Is it possible ? Is it already possible and I miss something ?
Thanks
The text was updated successfully, but these errors were encountered:
It's a deprecation -> use the deprecation-rules package. I don't see why not.
Sorry, something went wrong.
No branches or pull requests
I saw #151 was added by @villfa to check for non static data provider.
But I don't have the check on my project.
If I understand correctly, it's only active if https://github.com/phpstan/phpstan-deprecation-rules is installed.
But I'd like to have this rule even if I don't use the deprecation-rules package.
Currently stricter analysis (https://phpstan.org/config-reference#stricter-analysis) with PHPStan is possible
I'd like the same for the non-static check, ie: a config option to enable this rules (which would be automatically set to true if https://github.com/phpstan/phpstan-deprecation-rules is installed).
Is it possible ?
Is it already possible and I miss something ?
Thanks
The text was updated successfully, but these errors were encountered: