Content client package

[madsrasmussen]

The PR moves the Content, Content Type, and Property Type modules out of core and into their own package. In general, this doesn't impact packages since the import aliases remain the same: @umbraco-cms/backoffice/content, @umbraco-cms/backoffice/content-type and @umbraco-cms/backoffice/property-type.

The reason for the move is that the content module depends on the data type module. The data type module is not part of core; therefore, we can't depend on it. Now both packages are considered external, in relation to Core, meaning they can depend on each other.

Breaking Changes:

UmbWorkspaceHasCollectionCondition

• Renamed class and types to include Content since the condition was expecting a content collection workspace.
• Renamed constant UMB_WORKSPACE_HAS_COLLECTION_CONDITION_ALIAS to UMB_WORKSPACE_HAS_CONTENT_COLLECTION_CONDITION_ALIAS.
• Exports moved from @umbraco-cms/backoffice/workspace to @umbraco-cms/backoffice/content

UmbWorkspaceContentTypeAliasCondition

Before
import type { UmbWorkspaceContentTypeAliasConditionConfig} from '@umbraco-cms/backoffice/workspace';

After
import type { UmbWorkspaceContentTypeAliasConditionConfig} from '@umbraco-cms/backoffice/content-type';

UmbPropertyStructureWorkspaceContext

Before
import type { UmbPropertyStructureWorkspaceContext} from '@umbraco-cms/backoffice/workspace';
import { UMB_PROPERTY_STRUCTURE_WORKSPACE_CONTEXT } from '@umbraco-cms/backoffice/workspace';

After
import type { UmbPropertyStructureWorkspaceContext} from '@umbraco-cms/backoffice/content-type';
import { UMB_PROPERTY_STRUCTURE_WORKSPACE_CONTEXT } from '@umbraco-cms/backoffice/content-type';

[Copilot]

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

Files not reviewed (2)

• src/Umbraco.Web.UI.Client/package-lock.json: Language not supported
• src/Umbraco.Web.UI.Client/package.json: Language not supported