Content Types: Root properties

[nielslyngsoe]

Implements root properties for Content Types, which includes Blocks.

[Copilot]

Pull request overview

Implements support for “root properties” (properties not assigned to a tab/group container) across Content editing, Content Type design, and Block editing experiences.

Changes:

• Add root-properties detection (hasProperties) and use it to enable/show the root tab/routes in Content, Content Types, and Block workspaces.
• Extend property-structure resolution to treat containerId === null as “root” and return properties without a container.
• Adjust Content Type design tab rendering to allow containerId === null (root) to render the properties panel.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/Umbraco.Web.UI.Client/src/packages/content/content/workspace/views/edit/content-editor.element.ts	Enables root tab/routes when root properties exist (in addition to root groups).
src/Umbraco.Web.UI.Client/src/packages/content/content-type/workspace/views/design/content-type-design-editor.element.ts	Adds root-properties state/observation and uses it in routing + root tab rendering.
src/Umbraco.Web.UI.Client/src/packages/content/content-type/workspace/views/design/content-type-design-editor-tab.element.ts	Allows rendering the properties panel for containerId === null (root).
src/Umbraco.Web.UI.Client/src/packages/content/content-type/structure/content-type-structure-manager.class.ts	Includes “no container” properties when querying structures for containerId === null.
src/Umbraco.Web.UI.Client/src/packages/content/content-type/structure/content-type-property-structure-helper.class.ts	Adds explicit handling for containerId being undefined vs null vs string; supports root properties.
src/Umbraco.Web.UI.Client/src/packages/block/block/workspace/views/edit/block-workspace-view-edit.element.ts	Enables root route/tab when root properties exist, not just root groups.
src/Umbraco.Web.UI.Client/src/packages/block/block/workspace/views/edit/block-workspace-view-edit-content-no-router.element.ts	Treats root properties as a reason to default to the root tab when choosing initial active tab.

Comments suppressed due to low confidence (2)

src/Umbraco.Web.UI.Client/src/packages/content/content/workspace/views/edit/content-editor.element.ts:126

• When _hasRootProperties is true and _hasRootGroups is false, the root route/tab is now enabled, but #renderTab()’s active calculation still only considers _hasRootGroups. With root-properties-only + at least one real tab, navigating to the base path (${this._routerPath}/) will mark both the root tab (path=null) and the first real tab (index 0) as active. Update the active logic to also account for _hasRootProperties (e.g. only apply the “index===0 && base-path” fallback when there is no root tab, and add a root-properties equivalent for the root tab).

		if (this._hasRootGroups || this._hasRootProperties) {
			routes.push({
				path: 'root',
				component: () => import('./content-editor-tab.element.js'),
				setup: (component) => {

src/Umbraco.Web.UI.Client/src/packages/block/block/workspace/views/edit/block-workspace-view-edit.element.ts:122

• #createRoutes() now adds a root route when _hasRootProperties is true, but the default-route redirect logic below still checks only !this._hasRootGroups. In the “root-properties-only” case this can add an extra path: '' redirect route even though a path: '' component route already exists, making the route table inconsistent and dependent on route order. Consider updating the redirect condition to !this._hasRootGroups && !this._hasRootProperties (or otherwise avoid adding a second path: '' route when root is enabled).

		if (this._hasRootGroups || this._hasRootProperties) {
			routes.push({
				path: '',
				component: () => import('./block-workspace-view-edit-tab.element.js'),
				setup: (component) => {