Don't wrap single-config_object forms in a detail

Created on 24 April 2023, over 1 year ago

Problem/Motivation

Forms with only one configuration object, as defined by getEditableConfigNames(), still use a detail #type element for the configuration object wrapper. (At least, they do in the default implementation of getContainerTypeForDepth().)

This is an unnecessary HTML element for a form that is not going to have other container elements at that level.

Proposed resolution

If there is only one editable config object defined in getEditableConfigNames, both depth 0 (wrapper for all config object wrappers) and depth 1 (wrapper for all elements on a single config object) should be 0 in the default implementation of getContainerTypeForDepth().

πŸ“Œ Task
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States bvoynick

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

Comments & Activities

Production build 0.71.5 2024