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
It appears that analysis fails when PHPStan calls into the container, which attempts to use symfony/type-infoTypeResolver/StringTypeResolver to parse phpdocs. Specifically, StringTypeResolver hasn't been updated to PHPStan 2.0, so it's calling Lexer(), omitting the new required parameter.
Note that in this application, symfony/type-info is coming in as a transitive dependency of symfony/property-access -> symfony/property-info -> symfony/type-info. The application itself isn't directly using type-info, nor does it declare phpstan/phpdoc-parser in its dependencies. (phpstan/phpdoc-parser is not installed at all, except internally to phpstan.)
Since this appears to fail attempting to parse docblocks, I removed all phpdoc annotations from the specific file it's complaining about, but got the same result.
I will attempt to create a minimal test case later today and update this issue accordingly.
It appears that analysis fails when PHPStan calls into the container, which attempts to use
symfony/type-info
TypeResolver/StringTypeResolver
to parse phpdocs. Specifically,StringTypeResolver
hasn't been updated to PHPStan 2.0, so it's callingLexer()
, omitting the new required parameter.Note that in this application,
symfony/type-info
is coming in as a transitive dependency ofsymfony/property-access
->symfony/property-info
->symfony/type-info
. The application itself isn't directly usingtype-info
, nor does it declarephpstan/phpdoc-parser
in its dependencies. (phpstan/phpdoc-parser
is not installed at all, except internally to phpstan.)Since this appears to fail attempting to parse docblocks, I removed all phpdoc annotations from the specific file it's complaining about, but got the same result.
I will attempt to create a minimal test case later today and update this issue accordingly.
The text was updated successfully, but these errors were encountered: