You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: src/packages/data-type/workspace/data-type-workspace.context.ts
+22-4Lines changed: 22 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,24 @@ import {
30
30
}from'@umbraco-cms/backoffice/entity-action';
31
31
32
32
typeEntityType=UmbDataTypeDetailModel;
33
+
34
+
/**
35
+
* @class uUmbDataTypeWorkspaceContext
36
+
* @description - Context for handling data type workspace
37
+
* There is two overall code flows to be aware about:
38
+
*
39
+
* propertyEditorUiAlias is observed
40
+
* loads propertyEditorUi manifest
41
+
* then the propertyEditorSchemaAlias is set to what the UI is configured for.
42
+
*
43
+
* propertyEditorSchemaAlias is observed
44
+
* loads the propertyEditorSchema manifest
45
+
* if no UI is defined then the propertyEditorSchema manifest default ui is set for the propertyEditorUiAlias.
46
+
*
47
+
* This supports two cases:
48
+
* - when editing an existing data type that only has a schema alias set, then it gets the UI set.
49
+
* - a new property editor ui is picked for a data-type, uses the data-type configuration to set the schema, if such is configured for the Property Editor UI. (The user picks the UI via the UI, the schema comes from the UI that the user picked, we store both on the data-type)
0 commit comments