Closed mdevlamynck closed 1 year ago
Can you please add a unit test for this?
As this is a naming convention coming from doctrine/persistence, I actually suggest adding an utility in doctrine/persistence (meant to replace the one from doctrine/common) instead of duplicating the logic in each package wanting to remove a dependency on doctrine/common.
So @stof do you want me to create a separate PR to doctrine/persistence to add that utility then update my this PR?
As this is a naming convention coming from doctrine/persistence, I actually suggest adding an utility in doctrine/persistence (meant to replace the one from doctrine/common) instead of duplicating the logic in each package wanting to remove a dependency on doctrine/common.
That's a good idea, but I'm not sure it will help here since this library is supporting
"doctrine/persistence": "^1.3.3|^2.0|^3.0"
or it would require to drop both 1 and 2 support.
it would require to drop both 1 and 2 support.
Seems fine given the version constraints of v3, as well as the install statistics: https://packagist.org/packages/doctrine/persistence/stats
For moving ClassUtils to doctrine/persistence I opened https://github.com/doctrine/persistence/pull/326 We will need this to be merged/released first then.
Fixes #417.
This fixes ReferenceRepository::getRealClass() to match with the behaviour of the equiavlent function in doctrine\common ClassUtils::getRealClass().