Get the current translation within the wrapped field output

Setting to NR as there is a patch.

I can confirm the issue, the referenced entities are displayed in the original content of the parent entity, instead of using the current language selected for the page. The MR is fixing the issue.

Checked code and functionally tested on real project, let's move on +1

Besides, I'm uploading a static copy of the MR 10.

Using patch form #5 in combination with the solution from 🐛 Infinite loop when first available formatter extends FieldWrapperBase Fixed , still gives use infinite loop for entity reference fields.
The function getTranslationFromContext triggers the loop, therefore we used the default functions hasTranslation() & getTranslation().

Thanks all! Let's get this finished. Could someone please rebase this, incorporate the new branch changes and also discuss #6?

Generally the code from #6

+    if ($entity->hasTranslation($langcode)) {
+      $entity = $entity->getTranslation($langcode);
+    }

is a typical pattern, but we should please ensure it's needed here and not already inherited or handled somewhere down or up the trace.

Updated the patch from #5 as it doesn't apply on rc3.

Updated the patch from #5 as it didn't apply to rc3.
https://www.drupal.org/files/issues/2024-04-26/3344938-8.patch →

Mhm I got a ping from this issue but can't see any activity. Would anyone like to finish this perhaps?

@økse: Is
$this->entityRepository->getTranslationFromContext()
a typical pattern now vs. #7? What are the pro's and cons?

I'd like to finish this, but I'm unsure about that point (core references or docs for that?)

Also the MR seems to need a rebase. Thanks!

Patch from #8 is working and looking good.
It's better than what's suggested in #6 because getTranslationFromContext allows fallback languages to be selected which can be very useful for some projects.

MR rebased!

Perfect, thank you @DuaelFr!

Let's merge this.

Automatically closed - issue fixed for 2 weeks with no activity.