Add optional phpstan-doctrine integration for metadata resolution #33
+159
−13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JanTvrdik
force-pushed
the
phpstan-doctrine-integration
branch
6 times, most recently
from
7bc37d9 to
acbf030
Compare
When phpstan/phpstan-doctrine is installed and configured with an ObjectManager loader, the PHPStan extension now uses real Doctrine ClassMetadata for resolving association target types. This provides more accurate type inference for entities using XML/YAML mappings. Falls back to attribute-based resolution when metadata is unavailable.
JanTvrdik
force-pushed
the
phpstan-doctrine-integration
branch
from
acbf030 to
36a6ecd
Compare
janedbal
approved these changes
Dec 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
phpstan/phpstan-doctrine'sObjectMetadataResolverChanges
phpstan/phpstan-doctrinetorequire-devandsuggestEntityPreloaderCoreto accept optionalObjectMetadataResolverand try metadata resolution firstEntityPreloaderReturnTypeExtensionandEntityPreloaderRulewith constructorsrules.neonto service syntax for consistencyBenefits
Test plan