While I still think that the revisions / content moderation support is still a hairy problem-space to tackle, maybe we should support translations out-of-the-box, based on the assumption that:
If an entity is used by any translation of the host entity, we should track that usage, pointing to the default language (non-translated entity) on the report page.
I was a bit reluctant to assume this ^^ until now, but once I see that core is doing the same for file entities (at least at this moment in time), it shouldn't be a big deal if we go the same route and provide at least the same level of functionality.
Comment | File | Size | Author |
---|---|---|---|
#2 | 2921957-2.patch | 28.56 KB | marcoscano |
Comments
Comment #2
marcoscanoThis apparently works for me.
Comment #4
marcoscanoCommitted #2 to have this available right now, but let's add tests for it in the follow-up #2922418: Refactor multilingual tracking.