Detect unqualified static access in global scope #243
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Foo::class,Foo::method(), orFoo::CONSTANTin global scope when the class is not in$knownSymbols::classProblem
When using code like:
If
ThInCacheInterfacewas not in$knownSymbols, it would not be detected as a class usage. This caused packages to be incorrectly flagged as "unused dependencies".Solution
Added detection for unqualified class names followed by
::in global scope, similar to the existing handling for unqualified function calls.Test plan
::class,::staticMethod(), and::CONSTANTpatterns inglobal-namespace.phpextensions-global.phpexpectations forZipArchive::classwhich is now detectedcomposer checkpasses