- Issue created by @tstoeckler
- Status changed to Needs review
4 months ago 3:50pm 26 August 2024 - 🇩🇪Germany tstoeckler Essen, Germany
Did some very light Git archeology but wasn't able to find anything interesting. As far as I can tell this was duplicate already 9 years ago when it was introduced.
Also included the removal of a missing & unused use statement, but as a separate commit in case that's considered out of scope.
- 🇨🇭Switzerland berdir Switzerland
It is a duplicate right now, but maybe it shouldn't be? This does the lookup only by uuid, but we also store the revision id. the revision uuid field never landed in core, so it's difficult to replicate what the regular ER field does for revisions.
I think an ERR field with a default would be extremely rare, no idea what the use case for that would be, so we can maybe just ignore that.