A relationship to the content_moderation_state entity was previously the only way to display and filter the moderation state for moderated entities. Now, views support has been built into the computed moderation_state field directly.
Reasons that deprecating this feature is a good idea:
@internal and there is even discussions about removing it entirely.Since relationships are more a feature of the Drupal "product" than an API, that is, it would be perfectly reasonable for someone to install Drupal, configure the relationship on a view without writing any code it has to be treated differently to most API deprecations. To solve this, there are two warnings in the UI which will tell users they are either about to use a deprecated feature or have already used it:
The change record will have detailed steps required to configure the supported field based views integration and steps on how to remove the relationship.
For folks who have done something heavily customised or extended the internal entity type in some way, a link to a contributed project will be provided which adds the relationships back.
The net result: less code to support and less confused users in the queue who don't understand why this relationship is so broken.
Agree on the approach and commit.
Additional UI elements pictured above.
None.
None.
Fixed
8.9 ⚰️
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.