[FrameworkBundle][Translator] Fix cache warmer translator lazy-loading #23293
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.
Not really a bug fix, but in #23014, we expected to lazy load the cache warmer's translator by injecting the container instead. But the
LoggingTranslatorPass
replaces it, and it results in a deprecation raised in 3.4.The issue with this patch and the original PR intent however is that the translator you get from the container might be a decorated one (
DataCollectorTranslator
for instance) which may not implementWarmableInterface
, making the warmer ineffective...Considering #23014 issue mainly was about the
TemplateCacheWarmer
, I'm torn between this patch, reverting changes inTranslationsCacheWarmer
or finding some other ugly workarounds.