@contentchef/contentchef-types 11.0.0 → 11.1.0-alpha.1

package/lib/api/ContentDefinition.ts

@@ -1,6 +1,7 @@
 import { AuthorResponse } from './Author';
 import { PagedListResponse } from './common';
-import { ContentDefinitionSchema, Field, I18NDictionary } from './ContentDefinitionSchema';
+import { DefinitionMigrationState, FieldChanges } from './Component';
+import { ComponentMarker, ContentDefinitionSchema, ContentDefinitionSchemaInput, Field, I18NDictionary } from './ContentDefinitionSchema';
 import { Extension } from './Extension';
 
 /**
@@ -108,7 +109,7 @@ export type CreateContentDefinitionRequest = {
     /**
      * The content definition fields schema
      */
-    schema: ContentDefinitionSchema;
+    schema: ContentDefinitionSchemaInput;
 
     /**
      * will bypass content definition mnemonicId validation for every linked-content field
@@ -135,7 +136,7 @@ export type UpdateContentDefinitionRequest = {
     /**
      * The content definition fields schema
      */
-    schema: ContentDefinitionSchema;
+    schema: ContentDefinitionSchemaInput;
 
     /**
      * will bypass content definition mnemonicId validation for every linked-content field
@@ -189,6 +190,31 @@ export type ContentDefinitionResponse = {
      * Valued with paths to each array or null if definition is legacy
      */
     trackableArrayFields?: ArrayField[] | null;
+
+    /**
+     * The components the definition's managed fragments copy, one per component
+     */
+    components: ComponentMarker[];
+};
+
+/**
+ * This type represent one component a definition uses, as the get content definition API request
+ * describes it
+ */
+export type DefinitionComponent = ComponentMarker & {
+    /**
+     * The component latest version
+     */
+    latestVersion: number;
+    /**
+     * The archived status of the component
+     */
+    archived: boolean;
+    /**
+     * What upgrading from `version` to `latestVersion` would add, remove, change and rename, all empty
+     * when up to date. What it would do to the contents is only known by previewing it
+     */
+    changes: FieldChanges;
 };
 
 /**
@@ -202,7 +228,16 @@ export type UpdateContentDefinitionResponse = ContentDefinitionResponse;
 /**
  * This type represent the response of a get content definition API request
  */
-export type GetContentDefinitionResponse = ContentDefinitionResponse | undefined;
+export type GetContentDefinitionResponse = (Omit<ContentDefinitionResponse, 'components'> & {
+    /**
+     * The components the definition uses, each with its latest version and what upgrading to it changes
+     */
+    components: DefinitionComponent[];
+    /**
+     * Where the definition's contents stand in its migrations
+     */
+    migration: DefinitionMigrationState;
+}) | undefined;
 
 /**
  * This type represent the data needed to make a validate definition field API request
@@ -416,5 +451,8 @@ export enum SchemaFieldViolationCodes {
     translatableNotAllowed = 'translatableNotAllowed',
     invalidEnumValue = 'invalidEnumValue',
     compactCannotBeNested = 'compactCannotBeNested',
-    variantTypeNotAllowed = 'variantTypeNotAllowed'
+    variantTypeNotAllowed = 'variantTypeNotAllowed',
+    componentArchived = 'componentArchived',
+    componentNotPublished = 'componentNotPublished',
+    invalidComponentMarker = 'invalidComponentMarker'
 }

package/lib/api/ContentDefinitionSchema.ts

@@ -76,6 +76,46 @@ export type FragmentDefinition = {
      * The friendly labels of the fragment
      */
     labels?: I18NDictionary;
+    /**
+     * Set on a managed fragment: a copy of a component version, keyed by the component's mnemonic id,
+     * that the backend writes and nobody edits by hand. Saving a definition with the marker alone has
+     * the backend fill in labels and fields, and saving it with a later `version` upgrades the fragment
+     */
+    component?: ComponentMarker;
+};
+
+/**
+ * This type represent a content definition schema as the create and update content definition API
+ * requests take it, whose managed fragments may leave out their labels and fields
+ */
+export type ContentDefinitionSchemaInput = Omit<ContentDefinitionSchema, 'fragments'> & {
+    fragments: {
+        [name: string]: FragmentDefinition | ManagedFragmentInput;
+    };
+};
+
+/**
+ * This type represent a managed fragment as a definition save may send it: labels and fields left out
+ * are filled in from the component version, and labels and fields sent must be the version's
+ */
+export type ManagedFragmentInput = {
+    component: ComponentMarker;
+    labels?: I18NDictionary;
+    fields?: Field[];
+};
+
+/**
+ * This type represent the marker of a managed fragment, naming the component and the version it copies
+ */
+export type ComponentMarker = {
+    /**
+     * The component mnemonic id, which is also the fragment's key in the schema
+     */
+    mnemonicId: string;
+    /**
+     * The component version the fragment copies
+     */
+    version: number;
 };
 
 /**

package/lib/api/index.ts

@@ -3,6 +3,7 @@ export * from './AuditLog';
 export * from './Author';
 export * from './Channel';
 export * from './Content';
+export * from './Component';
 export * from './ContentDefinition';
 export * from './ContentDefinitionSchema';
 export * from './ContentExportImport';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentchef/contentchef-types",
-  "version": "11.0.0",
+  "version": "11.1.0-alpha.1",
   "description": "ContentChef types",
   "author": "PierpaoloIannone <piannone@byte-code.com>",
   "homepage": "https://github.com/ContentChef/contentchef-management-js-client#readme",
@@ -34,5 +34,5 @@
   "devDependencies": {
     "typescript": "^5.9.3"
   },
-  "gitHead": "4590d085381430e5b56e98a2dabdf03911d05e3e"
+  "gitHead": "8970d38d1236984dee510da19687d73078f76a70"
 }