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
Would be great if one could also ban single classes or even namespaces.
This is especially usefull when you wanne get rid of a external dependency in which you cannot annotate the classes itself with @deprecated as you dont own the code
If already supported: a example in the readme would be great
The text was updated successfully, but these errors were encountered:
I can see the benefits of this, such as if it would detect even just use imports. I'm working on a codebase where people still end up adding use Sensio\Bundle\FrameworkExtraBundle\Configuration\Route; though it (and other similar) classes/annotations have been deprecated for a while.
Would be great if one could also ban single classes or even namespaces.
This is especially usefull when you wanne get rid of a external dependency in which you cannot annotate the classes itself with
@deprecated
as you dont own the codeIf already supported: a example in the readme would be great
The text was updated successfully, but these errors were encountered: