Limit the concept of 'bundle' to ContentEntities ?

Created on 13 November 2013, over 11 years ago
Updated 25 October 2024, 9 months ago

The notion of "entity bundle" is currently baked in Entity / EntityInterface.

But I don't see a case for config entities to have different "bundles", at least 99% of them don't. Moreover, many of them store things about a specific (content entity) bundle, and thus include a 'bundle' property, which is different from "their own bundle", and thus has to be disambiguated (targetBundle() or something).

Now that we have ContentEntityBase & ContentEntityInterface, why don't we limit the notion of bundles to content entities ?

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

entity system

Created by

🇫🇷France yched

Live updates comments and jobs are added and updated live.
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.

  • 🇳🇿New Zealand quietone

    What is the actionable item in this issue?

    Since we need more information to move forward with this issue, I am setting the status to 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!

  • Status changed to Closed: outdated 2 months ago
  • 🇳🇿New Zealand quietone

    Since there has been no response to the query 7 months ago, I am closing this issue.

    If there is work to do here, then either re-open the issue or open a new issue and reference this one. If the choice is to use this issue then add a comment change make sure to change the issue status to 'Active'.

Production build 0.71.5 2024