Remove bundle usage if core patch 2987537 applied

Created on 6 December 2024, 5 months ago

There are multiple issues open in core related to the bundle key in the menu link content entity. Some seek to retain the bundle key and others remove it. This issue is intended to go hand-in-hand with the MR against https://www.drupal.org/project/drupal/issues/2987537 πŸ“Œ Custom menu link entity type should not declare "bundle" entity key Needs work , removing the bundle key use from menu_item_extras and addressing the warnings that result if that MR is applied.

πŸ“Œ Task
Status

Active

Version

3.1

Component

Code

Created by

πŸ‡¦πŸ‡ΊAustralia nigelcunningham Geelong

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @nigelcunningham
  • πŸ‡ΊπŸ‡¦Ukraine voleger Ukraine, Rivne

    Removal of bundle usage will break a lot of the existing system. Before the removal, we need to focus on the migration process:
    - The site owner must review the view/form mode configuration, as the menu item type might share the same name but differ in bundle configuration. All view/form modes should be defined in the menu_link_content bundle; thus, when the bundle definition is removed, the view/form mode will remain under the default configuration.
    - After completing the item above, the current menu items must adjust the view mode field to reflect each menu block's expected view mode.

    OTOH, removing the menu_link_content bundle in the core will not affect the projects using MenuItemsExtras as the project alters the menu_link_content entity definition. However, continuing to support the bundles may break compatibility with other contributed projects, which assume that menu_link_content is always single-bundled.

    We need to think about the scope before switching to the single bundle, as well as to keep support bundles in the menu_link_content entity.

Production build 0.71.5 2024