Content entities overviews list standard

Created on 23 December 2016, over 8 years ago
Updated 4 September 2025, 13 days ago

Problem/Motivation

We should also reflect a naming standard views entities lists. For example I work on " form_mode_manager β†’ " now and I have to add a button " LocalAction " on a few of entities . My main problem is really the parameter " APPEAR ON " because I have here "guess" the name of entities listings depending on the entity or I add my local actions. When we use the listings of entities we had a common element

'appears_on' => ["entity.{$entity_type_id}.collection"];
In order to identify the list in question and with his views we have nothing in common ... eg : node = > ' system.admin_content ' media = > ' view.media.media_page_list...

Actually that force persons to plug of each entities to considerate all specificity of each.

Proposed resolution

Can we discuss of it here or from right thing? what are your opinions ?

I think migrate with views is a good think ! But WE NEED to impose an clear way to naming on theses overviews page to permit a better manage.

I purpose an simple / clear naming like "view.{entity}.{$entity_type_id}.overview"

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

entity system

Created by

πŸ‡«πŸ‡·France woprrr

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024