Problem/Motivation
Follow-up for #2891215-31: Add a way to track whether a revision was default when originally created:
This morning there was an hangout call with @amateescu, @catch, @hchonov, @timmillwood and me. We discussed a few scenarios where a revision type would be useful. We all agreed there can be legitimate use cases for it, possibly even in core, however we could not conclusively come up with an example that would require such field in the short term. For this reason we decided to proceed with a boolean flag (default_revision: 0/1) and evaluate the need for an additional revision type field in a later stage, when we either require it in core, or there is a strong use case in contrib. This new field would typically be used to describe the "owner" module, but it actually would be a machine name, so more complex use cases could be addressed.
Proposed resolution
Add a revision_type string field.
Remaining tasks
Come up with a strong-enough use case to justify adding this field in core.
User interface changes
None
API changes
Only additions: RevisionableInterface::getRevisionType().
Data model changes
A new revision_type will be created for all revisionable entity types.
Comments
Comment #13
smustgrave commentedThe parent issue landed 8 years ago, around the same time as this ticket. So is it still needed?