@terminalfour/terminalfour-js 1.0.0 → 1.0.1

package/dist/cjs/resources/content-type-resource.d.ts

@@ -242,7 +242,13 @@ export declare class ContentTypeResource {
         /** Field names to remove from the content type */
         removeFields?: string[];
     }): Promise<ContentType>;
-    /** Deletes a content type by ID. */
+    /**
+     * Deletes a content type by ID.
+     *
+     * System content types (`type === 30`) are managed by T4 and back core
+     * features; deleting one can break the instance, so this is blocked with a
+     * clear error. There is no override.
+     */
     delete(id: number): Promise<void>;
     /** Creates a new content type. */
     create(data: {

package/dist/cjs/resources/content-type-resource.js

@@ -822,8 +822,23 @@ class ContentTypeResource {
         await ct.save();
         return ct;
     }
-    /** Deletes a content type by ID. */
+    /**
+     * Deletes a content type by ID.
+     *
+     * System content types (`type === 30`) are managed by T4 and back core
+     * features; deleting one can break the instance, so this is blocked with a
+     * clear error. There is no override.
+     */
     async delete(id) {
+        const raw = await this.httpClient.request({
+            method: 'GET',
+            path: `/contenttype/${id}`,
+        });
+        if (raw.type === SYSTEM_CONTENT_TYPE) {
+            const name = (0, utils_js_1.decodeHtmlEntities)(raw.alias || raw.name);
+            throw new Error(`Cannot delete content type "${name}" (${id}) because it is a system content type. ` +
+                'Deleting system content types is not allowed.');
+        }
         await this.httpClient.request({
             method: 'DELETE',
             path: `/contenttype/${id}`,

package/dist/esm/resources/content-type-resource.d.ts

@@ -242,7 +242,13 @@ export declare class ContentTypeResource {
         /** Field names to remove from the content type */
         removeFields?: string[];
     }): Promise<ContentType>;
-    /** Deletes a content type by ID. */
+    /**
+     * Deletes a content type by ID.
+     *
+     * System content types (`type === 30`) are managed by T4 and back core
+     * features; deleting one can break the instance, so this is blocked with a
+     * clear error. There is no override.
+     */
     delete(id: number): Promise<void>;
     /** Creates a new content type. */
     create(data: {

package/dist/esm/resources/content-type-resource.js

@@ -817,8 +817,23 @@ export class ContentTypeResource {
         await ct.save();
         return ct;
     }
-    /** Deletes a content type by ID. */
+    /**
+     * Deletes a content type by ID.
+     *
+     * System content types (`type === 30`) are managed by T4 and back core
+     * features; deleting one can break the instance, so this is blocked with a
+     * clear error. There is no override.
+     */
     async delete(id) {
+        const raw = await this.httpClient.request({
+            method: 'GET',
+            path: `/contenttype/${id}`,
+        });
+        if (raw.type === SYSTEM_CONTENT_TYPE) {
+            const name = decodeHtmlEntities(raw.alias || raw.name);
+            throw new Error(`Cannot delete content type "${name}" (${id}) because it is a system content type. ` +
+                'Deleting system content types is not allowed.');
+        }
         await this.httpClient.request({
             method: 'DELETE',
             path: `/contenttype/${id}`,

package/docs/content-types.md

@@ -231,6 +231,8 @@ Delete a content type through the resource:
 await t4.contentTypes.delete(44);
 ```
 
+System content types cannot be deleted — see [System content types](#system-content-types) below.
+
 ## System content types
 
 System content types are managed by T4 and back core features. Removing or renaming their elements can break the instance, so the SDK blocks both on `save()` (and through `update({ removeFields })`):
@@ -249,10 +251,22 @@ On a system content type you can still:
 - Change an element's `maxSize`
 - Change the content type's `description` and any element's `description`
 
-Two system content types are exempt, because removing and renaming their elements is safe: the **Section Metadata** content type and the **Extended User** content type. On those two, removal and renaming work exactly like a regular content type.
+Two system content types are exempt from the element removal and renaming guard, because removing and renaming their elements is safe: the **Section Metadata** content type and the **Extended User** content type. On those two, removal and renaming work exactly like a regular content type.
 
 The check runs when you call `save()` or `update()`, not when you call `removeField()`. Because `removeField()` only stages the change in memory, nothing is sent to T4 when the guard blocks a save.
 
+### Deleting a system content type is always blocked
+
+`delete()` refuses to delete **any** system content type, with no exceptions. Deleting a system content type outright (rather than editing its elements) can break instance-wide features, so there is no override:
+
+```typescript
+await t4.contentTypes.delete(systemTypeId);
+// Error: Cannot delete content type "..." (<id>) because it is a system
+// content type. Deleting system content types is not allowed.
+```
+
+`delete()` fetches the content type first to check its type; if it is a system content type, nothing is deleted.
+
 ## Manage content layouts
 
 Access layouts through `layouts` on a `ContentType`. Layout operations use names; layout IDs are not exposed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@terminalfour/terminalfour-js",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "JavaScript / TypeScript SDK for the Terminalfour Web Services REST API",
   "keywords": [
     "terminalfour",
@@ -59,7 +59,7 @@
     "@types/node": "^25.5.2",
     "fast-check": "^4.1.1",
     "typescript": "^5.7.0",
-    "vitest": "^3.2.1"
+    "vitest": "^5.0.0"
   },
   "license": "Elastic-2.0"
 }