You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine we have two classes AbstractEvent and SpecificEvent extends AbstractEvent. AbstractEvent has getString method, SpecificEvent uses it. One day we decide this method shoud be placed in SpecificEvent but not in AbstractEvent and we create one more getString method in SpecificEvent and make AbstractEvent::getString deprecated. So we have the child class with the method and the parent class with the same deprecated method.
Bug report
Imagine we have two classes
AbstractEvent
andSpecificEvent extends AbstractEvent
.AbstractEvent
hasgetString
method,SpecificEvent
uses it. One day we decide this method shoud be placed inSpecificEvent
but not inAbstractEvent
and we create one moregetString
method inSpecificEvent
and makeAbstractEvent::getString
deprecated. So we have the child class with the method and the parent class with the same deprecated method.Code snippet that reproduces the problem
https://phpstan.org/r/4ff86893-71fd-46a6-8f53-ddef9a049d0d
Expected output
I think
SpecificEvent::getString
should not be deprecated.The text was updated successfully, but these errors were encountered: