Do not configure deprecated proxy options when native lazy ghost objects are enabled #1898
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
mbabker
force-pushed
the
proxy-config-deprecations
branch
from
f4344bc to
c50ce02
Compare
ostrolucky
approved these changes
Jul 3, 2025
greg0ire
approved these changes
Jul 3, 2025
stof
approved these changes
Jul 7, 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.
Partially addresses #1895
This will stop calling the ORM Configuration class' deprecated
setAutoGenerateProxyClasses(),setProxyDir(), andsetProxyNamespace()methods when the native lazy objects feature is enabled and soft-deprecates the relevant config options by noting they'll be ignored in this case. This purposely only stops calling those methods with ORM 3.5 since 3.4 doesn't have the deprecation notices and issues like doctrine/orm#11997 meant with 3.4.0 specifically there were a couple of cases where not configuring them led to errors.