Dispatch events for changing content moderation states

Created on 27 April 2017, about 8 years ago
Updated 26 April 2023, about 2 years ago

Problem/Motivation

The ContentModerationState entity type is @internal so any time users interact with it directly, they are risking API breaks. One of the convenient touch points with the entity is implementing hook_entity_(insert|update) as seen in the content_moderation_notifications. Implementing these hooks gives you a single place to react to content states changes.

Proposed resolution

Provide an alternative to these hooks so users have a consistent and @api way to react to any item of content having its state changed. An event suits this purpose nicely.

Remaining tasks

Review and commit.

User interface changes

None.

API changes

An additional event.

Data model changes

πŸ“Œ Task
Status

Needs review

Version

10.1 ✨

Component
Content moderationΒ  β†’

Last updated 1 day ago

  • Maintained by
  • πŸ‡¦πŸ‡ΊAustralia @Sam152
Created by

πŸ‡¦πŸ‡ΊAustralia Sam152

Live updates comments and jobs are added and updated live.
  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024