-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Is it possible to check for use of deprecated classes? #43
Labels
phpstan-deprecation-rules
Issue related to the Deprecation Rules extension
upstream
Ticket involves dependencies
Comments
Ah, interesting. This definitely needs to be moved to phpstan-drupal. Or kept here and a mirror opened (I need to decide how I want to manage that.) The root detection is phpstan-deprecation-rules. The investigation would need to check there for passing deprecated classes into a constructor. |
mglaman
added
upstream
Ticket involves dependencies
phpstan-deprecation-rules
Issue related to the Deprecation Rules extension
labels
Apr 26, 2019
See mglaman/phpstan-drupal#321 as well |
So should this issue be in |
This got fixed a while ago in phpstan-drupal |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
phpstan-deprecation-rules
Issue related to the Deprecation Rules extension
upstream
Ticket involves dependencies
So I ran this on one of my contrib modules:
But I know that I have overridden constructors populating parameters with deprecated services, such as:
phpStorm lines out
EntityManagerInterfaceand I learned at DruaplCon and via Slack from Alex Pott that this should be refactored to drop the constructor entirely, putting the custom service population increate()
Can we catch instantiation or passing of deprecated objects in addition to deprecated methods?The text was updated successfully, but these errors were encountered: