[policy] Bundle / field name / view mode theme suggestions can conflict

Created on 28 November 2016, almost 9 years ago
Updated 27 August 2025, 2 days ago

Problem/Motivation

#1367354: The list of theme hook suggestions for "field" is incorrectly ordered and has namespacing collisions is a pre-existing issue with field template suggestions.

Introduce generic entity template with standard preprocess and theme suggestions Needs work is a new issue adding generic entity template suggestions that could run into the same issue.

We need to figure out whether to namespace suggestions (i.e. bundle-$suggestion or b-$suggestion) and which format to use to prevent the potential for conflicts. This would also allow the targeting of the template to be figured out from the filename rather than just the logic in the theme registry building.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🌱 Plan
Status

Active

Version

11.0 🔥

Component

theme system

Created by

🇬🇧United Kingdom catch

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.

  • 🇨🇭Switzerland berdir Switzerland

    4 years later...

    I think this is not a duplicate, but the meta issue of that or maybe better, a policy issue on whether or not we should do prefixes, it also references the entity issue that was essentially blocked on this.

    I did make a specific proposal with a few questions in 🐛 Incorrect order and duplicate theme hook suggestions Needs work and would appreciate feedback there, but I think this is still an issue that should have its own resolution on whether or not we use prefixes or not, and if all entries should use prefixes or only less common ones, likely guided by the specific examples in the field issue.

Production build 0.71.5 2024