Support entity translation

Hmmm, interesting idea, but this seems like it would break the functionality for sites that aren't multilingual. Is there a way it could make the langcode optional, and use the site default language if it isn't provided? Or alternatively, maybe it could provide the language-specific path as an alternative to the current one?

When I wrote the patch I was quite in a hurry to deliver something usable in the site it needed, sorry for its half-baked state.

Is there a way it could make the langcode optional, and use the site default language if it isn't provided?

Initally I was thinking about an optional parameter → , but being it "dynamic" this wouldn't work well.

Maybe with a Parameter converter? → . I never used them, but that could perhaps solve the problem. The LanguageConverter mentioned in the documentation could be exactly what is necessary.
If I'll have some spare time I'm going to check it out.

Or alternatively, maybe it could provide the language-specific path as an alternative to the current one?

Sorry, I do not understand this idea. What do you mean?

Or alternatively, maybe it could provide the language-specific path as an alternative to the current one?

Sorry, I do not understand this idea. What do you mean?

I was suggesting that the existing route could be left as is, and a new, language-specific route could be added.

I've updated the patch for the last version of the module changing che logic as comment #6 :
The existing route is untouched (although, I moved the code in a common method between the two controller's function) and a new route is added.

This patch also has two fixes that should be in another issue:

1. Line 62 of ContentModerationLinkController.php $storage = $this->entityTypeManager->getStorage($type); should be $storage = $this->entityTypeManager()->getStorage($type);
2. Line 104 of same class, $valid_transitions = $this->validator->getValidTransitions($entity, $account); will break if the content is not moderated. isModeratedEntity() of service content_moderation.moderation_information should be checked before - or any other solution

Re-roll of patch #6