phpstan-banned-code Support class bann rules

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

Mar 07 '20 06:03 staabm

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.

follow-up: It appears that https://github.com/spaze/phpstan-disallowed-calls/pull/51 may be able to support this

Feb 18 '21 15:02 alister

Please try https://github.com/spaze/phpstan-disallowed-calls/tree/v1.3.0 as it supports this now.

Feb 20 '21 07:02 ruudk