Revision log interface

[dawehner]

Just like node provides revision logs it would be nice for entity types
to provide such a feature.

[bojanz]

Such an interface should have a matching trait?

Don't all revisionable entities have to have a revision log? In which case it might make more sense to have a bigger interface with getters/setters for revision log, revision author, revision creation time?

[dawehner]

Don't all revisionable entities have to have a revision log? In which case it might make more sense to have a bigger interface with getters/setters for revision log, revision author, revision creation time?

I mean I don't care that much at all. The usecase I currently have does not need revision log, as its never something actually created by users in the first place

[bojanz]

Quoting Dick on IRC:
"I see, yeah that makes sense. But I think there will be the same arguments about both revision author, and revision created from other use cases and angels. e.g. someone will want revision log, but not doesn't need to track revision author
but in all honesty it's not too important to me. But fago was just very clear that he wanted the enhancers to be quite/very opinionated... I guess so that we don't end up with another 1000 interfaces in the Entity API"

So he's in favor of having one interface for all three.

[Berdir]

+1. We can just document on the interface that those methods can return NULL if they don't have that information.

[dawehner]

Alright consensus yeah! See us in #5