Why do hidden fields become a dependency in entity_view_display configs?

Created on 18 March 2022, over 2 years ago
Updated 28 July 2024, about 1 month ago

This is just a question about a design decision that was made in 2080823 β†’ that I don't fully understand. When we add a new field to a node type in our installation profile, we find that ALL the display mode configs for that node type now need to be updated/reverted even if the new field only shows up in 1-2 display modes of that node type because all the other display modes now pick up a setting to hide the new field.

<!--break-->

Why is this? It would seem that fields are hidden by default, so why is it important that a dependency be added on a field that isn't even shown?

I am filing this as a support request rather than a feature request because it does seem intentional and I did not come across other issues that describe this behavior as being undesirable, so I believe I am just not understanding the importance of this.

πŸ’¬ Support request
Status

Closed: outdated

Version

11.0 πŸ”₯

Component
ConfigurationΒ  β†’

Last updated 1 day ago

Created by

πŸ‡ΊπŸ‡ΈUnited States GuyPaddock

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.

Production build 0.71.5 2024