Differentiate pending/old revisions and default translations

I've made a first attempt at that. It could be cleaned up a little and the testing increased, but I was hoping to get some initial feedback on the overall approach before going further with the polish...?

Thanks!

Attaching a patch for composer from 8eab48f6e2443ecfd899a61e93f26c700940c2b1, thanks!

Thanks for contributing!

I agree this would be a nice addition to the usage page, and I'm onboard with adding this to the module. I left a comment on the code about improving wording on the UI text, but apart from that I don't see big red flags.

It would be important to add test coverage to all new scenarios we are adding, combinations of languages, pending/past revisions, etc.

Thanks!

Thanks so much, glad to hear this could make its way into the module! Agree that tests are needed, and I'll get on that over the next few days.

Btw just in case you hadn't seen, but there seems to be a layout-builder related failure with D10.1 which I think is entirely unrelated to this MR, see eg https://www.drupal.org/pift-ci-job/2692049 → ... had me well confused yesterday wondering what I'd broken ;)

Attaching a patch for composer from 6bfb4d583fbe3684cd73abb73ea995a414ee1b80, thanks!

We will need to add a test for and fix 🐛 Usages that have no revisions show up as "Translations or Previous Revisions" Fixed as that one went in without a test and caused a conflict when I rebased the MR.

Good news is the manual testing shows that this issue was a fix for 🐛 Usages that have no revisions show up as "Translations or Previous Revisions" Fixed too! Now to add some automated test coverage.

Added test coverage

Looks good to me, thanks both for contributing!

Tagged a new release with this 👍

Agree that tests are needed, and I'll get on that over the next few days.

🙄

Thanks @alexpott!

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