Problem/Motivation
If an entity does not have langcode the results are empty when accessing the revisions. i.e. Profile entity. See #2634230: Remove langcode entity key

Proposed resolution
Do not verify the langcode when building the rows. I have attached a patch.
Here is the result:

| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 2951528-7.patch | 1.17 KB | jsacksick |
| #5 | 2951528-no-langcode-revisions.patch | 992 bytes | bradjones1 |
| revisions-entity-without-langcode.patch | 1.91 KB | marthinal | |
| Screen Shot 2018-03-09 at 13.33.39.png | 157.64 KB | marthinal | |
| Screen Shot 2018-03-09 at 13.34.01.png | 246.53 KB | marthinal |
Comments
Comment #2
marthinal commentedComment #3
marthinal commentedComment #4
bojanz commentedNodeController has the same code, we need to be careful about removing it.
Might make more sense to add an additional check that skips the others when there's no langcode.
Comment #5
bradjones1I had put a PR against this project a long time ago at https://github.com/fago/entity/pull/46/files but development moved back to d.o...
Here's a re-rolled version to kick off some discussion.
Comment #6
jsacksick commentedWhy not doing just this instead?
Comment #7
jsacksick commentedComment #9
bojanz commentedI'd usually prefer some test coverage, but this is blocking Profile, and I'm hoping we deprecate all of this once Drupal 8.8 is released and has its own revision UI.
Thanks everyone!