Target langcode and source can be different

It would be necessary to look for a way to obtain the language efficiently, we are not sure if this one.

In this approach, we get the language from the prefix, the problem is that the target language was obtained from the source, and they don't have to match. This strategy works if the path has a prefix.

\Drupal\entity_mesh\EntityRender::setTargetFromHref

    if ($target->getLinkType() == 'internal' && $this->ifProcessInternalTarget()) {
      $this->processInternalHref($target, $source->getSourceEntityLangcode() ?? '');

I have eliminated the langcode in many places, since it was not used more than later to do a “setEntityLangcode” to the Target object, so for that, you do the set before, in the “public function processHrefAndSetComponents(string $href) {” and remove the langcode parameter in many places.

https://git.drupalcode.org/project/entity_mesh/-/merge_requests/5/diffs#...

  public function getTargetLangcodeFromPath(mixed $path) {
    $path = '/' . ltrim($path, '/');
    foreach ($this->prefixes as $langcode => $prefix) {
      if ($prefix && str_starts_with($path, '/' . $prefix . '/')) {
        $this->setEntityLangcode($langcode);
      }
    }

    return $this->targetEntityLangcode;
  }

I’ve only made one modification, which is extracting the logic that calculates the language prefix from the target object to the Repository service, as it’s also needed during the processing of redirects.

Could you please take a look and do a quick QA? Thanks!

Merged, Fixed!!

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