- 🇺🇸United States Chris Matthews
From @catch in the #yes-no-queue channel in Drupal Slack re: this functionality in Core:
I have a knee jerk reaction against it. I understand using it for commerce where you want to reference a product frozen in time on an order and similarish accounting stuff, it makes me uneasy for content workflow things for reasons similar to the ones fabianx gives on there. This doesn't mean it shouldn't be supported but I think the issue summary needs better pros and cons.
- 🇺🇸United States R_H-L
Given that entity_reference_revisions is currently the 6th most installed across the current codebase, I'd say the demand is there for the functionality to be in core. It's useful in a few places, such as referencing certain revisions of custom content entities as we do in custom blocks for Layout builder, but I admit ours is a corner case. Paragraphs uses this same model and without being able to reference a revision of a child element, reversion is complicated.