@terminalfour/terminalfour-js 1.0.2 → 1.0.3

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

@@ -242,11 +242,15 @@ export declare class ContentTypeResource {
         /**
          * Existing fields to modify, matched by `name`. Only the provided
          * properties are changed; omitted ones are left as-is. Use this to change
-         * an element's length (`maxSize`), description, or its `required`/`shown`
-         * flags. Throws if a named field does not exist on the content type.
+         * an element's length (`maxSize`), description, its `required`/`shown`
+         * flags, or to rename it with `newName`. Throws if a named field does not
+         * exist on the content type. Renaming an element on a system content type
+         * is blocked (except the Section Meta Data and Extended User types).
          */
         updateFields?: Array<{
             name: string;
+            /** New name for the element. Renames are blocked on system content types. */
+            newName?: string;
             maxSize?: number;
             description?: string;
             required?: boolean;

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

@@ -823,6 +823,14 @@ class ContentTypeResource {
                     field.required = change.required;
                 if (change.shown !== undefined)
                     field.shown = change.shown;
+                // Rename last: save() detects the change against the element's _elementId
+                // link and applies the system content type rename guard. Re-key the
+                // fields record so the returned model is addressable by the new name.
+                if (change.newName !== undefined && change.newName !== change.name) {
+                    field.name = change.newName;
+                    ct.fields[change.newName] = field;
+                    delete ct.fields[change.name];
+                }
             }
         }
         if (data.removeFields) {

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

@@ -242,11 +242,15 @@ export declare class ContentTypeResource {
         /**
          * Existing fields to modify, matched by `name`. Only the provided
          * properties are changed; omitted ones are left as-is. Use this to change
-         * an element's length (`maxSize`), description, or its `required`/`shown`
-         * flags. Throws if a named field does not exist on the content type.
+         * an element's length (`maxSize`), description, its `required`/`shown`
+         * flags, or to rename it with `newName`. Throws if a named field does not
+         * exist on the content type. Renaming an element on a system content type
+         * is blocked (except the Section Meta Data and Extended User types).
          */
         updateFields?: Array<{
             name: string;
+            /** New name for the element. Renames are blocked on system content types. */
+            newName?: string;
             maxSize?: number;
             description?: string;
             required?: boolean;

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

@@ -818,6 +818,14 @@ export class ContentTypeResource {
                     field.required = change.required;
                 if (change.shown !== undefined)
                     field.shown = change.shown;
+                // Rename last: save() detects the change against the element's _elementId
+                // link and applies the system content type rename guard. Re-key the
+                // fields record so the returned model is addressable by the new name.
+                if (change.newName !== undefined && change.newName !== change.name) {
+                    field.name = change.newName;
+                    ct.fields[change.newName] = field;
+                    delete ct.fields[change.name];
+                }
             }
         }
         if (data.removeFields) {

package/docs/content-types.md

@@ -167,6 +167,8 @@ await t4.contentTypes.update(44, {
 });
 ```
 
+> **Warning:** Removing a field deletes that element's content from every content item using this content type, and it cannot be recovered. Only remove a field when you're certain the data is no longer needed. To change a field's length, description, or name, use `updateFields` rather than removing and re-adding.
+
 Change properties of existing fields with `updateFields`. Fields are matched by `name`, and only the properties you supply are changed — anything you omit is left as-is. This is how you increase an element's length (`maxSize`):
 
 ```typescript
@@ -178,7 +180,20 @@ await t4.contentTypes.update(44, {
 });
 ```
 
-`updateFields` can change `maxSize`, `description`, `required`, and `shown`. It throws if a named field does not exist on the content type, and (like the other field operations) nothing is sent to T4 when it throws. To change a field's *type* or *name*, remove it and add a new one instead.
+Rename an existing element with `newName`. The field is matched by its current `name`, and you can rename and change other properties in the same entry:
+
+```typescript
+await t4.contentTypes.update(44, {
+  updateFields: [
+    { name: 'Title', newName: 'Headline' },
+    { name: 'Summary', newName: 'Teaser', maxSize: 300 },
+  ],
+});
+```
+
+After a rename, the returned content type is addressable by the new name (`ct.fields['Headline']`); the old key no longer exists.
+
+`updateFields` can change `maxSize`, `description`, `required`, `shown`, and `newName` (rename). It throws if a named field does not exist on the content type, and (like the other field operations) nothing is sent to T4 when it throws. Renaming an element on a system content type is blocked, except on the Section Meta Data and Extended User types (the same rule that applies to renames through the mutable pattern). It's currently not possible to change a field's *type*.
 
 `updateFields`, `removeFields`, and `addFields` can be combined in a single call; updates are applied first, then removals, then additions.
 
@@ -240,6 +255,8 @@ contentType.removeField('Old Field');
 await contentType.save();
 ```
 
+> **Warning:** `removeField()` deletes the element's content from every content item using this content type once you `save()`, and it cannot be recovered. Prefer `updateFields` (or mutating the field directly) to change a field's length, description, or name.
+
 Delete a content type through the resource:
 
 ```typescript

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@terminalfour/terminalfour-js",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "JavaScript / TypeScript SDK for the Terminalfour Web Services REST API",
   "keywords": [
     "terminalfour",