Entity.add...Revision

[CarolinJaser]

Mutation to replace legacy mutation which is doing the same thing. It should include:

changes
content
shouldReview
subscriptionSetEmail
subscriptionNotify (or a better name)
entityId
metaDescription
metaTitle
title

[hugotiburtino]

Since the revisions can have different fields (v.g. article has title, content, meta_title, meta_description, while course page has only title, content), the suggested mutation has to be splitted into many in order to have something similar to type check of the payload. In that case, we will have something like AddArticleRevisionMutation and AddCoursePageRevisionMutation

[elbotho]

Could the mutation accept a union type?

edit: not really it seems -.-

[hugotiburtino]

Could the mutation accept a union type?
edit: not really it seems -.-

No, it doesn't. Also not interface. It is quite frustating.

But anyways, instead of many mutations, I thought it would be tidier to put them all in the EntityMutation namespace. So, we will have EntityMutation.addCoursePageRevision, EntityMutation.addArticleRevision and so on.