- Issue created by @barry_fisher
- Merge request !111Add original_language to entity_info metadata when processing an entity URL → (Open) created by barry_fisher
- 🇩🇪Germany gbyte Berlin
We are careful with adding too much meta information because of memory constraints. The issue you linked is fair enough, I'll see if it makes sense to add bundle information; but in this case I feel like it's too much of an esoteric use case. Feel free to argue why you need the language info; closing this for now.
- 🇬🇧United Kingdom barry_fisher
Hello @gbyte. Fair enough - I understand the esoteric use case here and the balance required for a general use case.
For background, we want to remove any links that are no in the original language because we're using hreflang translation sets which have links to any translations. This causes a lot of duplication to entities included in the list, especially as we have 8 translations on the site we're working on.
As an alternative solution, would you consider a hook/event based solution which allows custom modules to implement alterations to the return value of
EntityUrlGenerator::processEntity()?