Problem/Motivation
When #2922033: Use the Layout Builder for EntityViewDisplays is committed, Layout Builder will hide the ability to manage field display with the Field UI in the "Manage Display" tab, by replacing every Entity Type's entity_view_display class with its own.
While the user experience provided by Layout Builder is superior to the traditional Field UI, some Entity Types or bundles may want to "opt-in" of this functionality, for a variety of reasons:
- A contrib module that enhances Field UI, like Field Group, is used
- An Entity Type uses a custom entity_view_display class with logic specific to itself
- An Entity Type or bundle isn't advanced enough for Layout Builder to make sense - i.e. it only has a handful of fields that do not need a layout
- It could be confusing for users to suddenly have all their displays converted to the Layout Builder UI
- As a result of the above the migration path to Layout Builder (from both Core Field UI and from c ontributing modules such as Panalizer) could be hindered somewhat and less smooth
Proposed resolution
Layout Builder will no longer be required by every bundle, but will be opt-in
Remaining tasks
Write the confirmation form
Update tests
User interface changes
Undecided.
API changes
Undecided.
Data model changes
Undecided.