Closed (fixed)
Project:
Drupal core
Version:
8.4.x-dev
Component:
content_moderation.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Feb 2017 at 09:47 UTC
Updated:
28 Apr 2017 at 07:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
timmillwoodIf we remove the dependency of revisions it won't be possible to have a draft of a published entity, aka "forward revision".
We could have a warning on non-revisionable entity forms to say "setting this to draft will unpublish the entity".
Comment #3
amateescu commentedHowever, this would defeat the purpose of Content Moderation and its concept of multiple states, no? :)
Comment #4
timmillwoodYou could say the same about only supporting EntityPublishedInterface entities.
Comment #5
alexpottYou can have multiple states without revisions. We have published and unpublished in core without revisions. You only need revisions for forward revisions. As far as i can see, content moderation does have to have forward revisions.
Comment #6
sam152 commentedAttached is a test. From what I can see, leaving off the "bundle" entity key is enough to ensure there is no bundle added, even when extending EntityTest. It defaults the bundle to the same name as the entity type ID for most purposes, except for when creating the entity fields.
The issue for removing the dependency on revisions is here #2850627: Do not require a revisionable entity type when using content_moderation..
Comment #7
Pavan B S commentedRerolled the patch.
Comment #8
timmillwoodDid it really need a re-roll? and looks like the new patch is now missing a main part?
Looks like a credit mining attempt to me.
Leaving as "Needs review" because #6 still seems valid. Reviews are often much more helpful than broken patches.
Comment #9
damiankloip commentedYes - It's missing the main part, and doesn't have the correct changes for the test assertions either. So it's not a reroll anyway, it's a re-make... Either way, the patch from #6 still APPLIES FINE.
These cheap commit mining attempts need to stop. It holds up issues, confuses people, as well as holding up the test bot when it could be testing useful patches.
Valuebound --
Comment #11
timmillwoodComment #12
timmillwoodRe-uploading #6 for clarity.
Suggested commit:
Comment #13
wim leersI was going to say: surely there already is such an test entity type… but no, there isn't! Great addition :)
Comment #14
timmillwood@Wim Leers - I think everyone has been too dependent on copy&paste when creating new entity_test entity types.
Comment #15
alexpottCommitted and pushed 0aa52f7 to 8.4.x and 8104932 to 8.3.x. Thanks!
As per discussion on the issue I did not credit @Pavan B S.