Initialize proxy objects if necessary #64
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.
In some cases, where no property of a lazy-loaded entity is accessed before trying to access/serialize the translations, the bundle will fail with the following error message:
No locale has been set and current locale is undefined.
The issue is that the
AssignLocaleListener
is not called if an entity is never actually loaded from the database, but only referenced through a doctrine proxy object.A dirty workaround is to access a property before fetching the translations, so instead of doing
We can do the following:
Obviously that's not a great workaround. This PR ensures that the proxies are properly initialized by doctrine before trying to load the translations instead by checking if an entity is a non-initialized proxy and, if it is, initialize it first.