creght-cli 0.7.4 → 0.7.6

package/README.md

@@ -410,19 +410,12 @@ creght content update --site_id=<project_id>/<site_id> --collection=blogs --id=<
 creght content delete --site_id=<project_id>/<site_id> --collection=blogs --id=<content_id>
 ```
 
-`--data` can point to either a plain CMS content body or a full content object. A plain content body may include a business field named `body`. The CLI treats JSON as a full content object only when it includes wrapper fields such as `id`, `slug`, `content_app_id`, `json_schema`, `status`, `sort`, or `tags`.
-
-If your business JSON has a top-level `slug`, do not pass it as plain body JSON because `slug` is a content wrapper field. Either pass the slug as a flag and omit it from `--data`:
-
-```bash
-creght content create --site_id=<project_id>/<site_id> --collection=prompts --data=./content-body.json --slug=typography-v02
-```
-
-Or use a full content object and put business fields under `body`:
+`--data` must be a full content object whose business fields sit under an object-valued `body` key. This is the only accepted format — a bare body is rejected with a format error, because guessing between the two shapes silently dropped fields whenever the body itself contained a name like `tags`, `slug`, or `sort`.
 
 ```json
 {
   "slug": "typography-v02",
+  "sort": 15,
   "body": {
     "title": "Typography V.02",
     "description": "100vh",
@@ -431,6 +424,19 @@ Or use a full content object and put business fields under `body`:
 }
 ```
 
+Top-level `slug` and `sort` are optional; the `--slug` / `--sort` flags override the file only when actually passed:
+
+```bash
+creght content create --site_id=<project_id>/<site_id> --collection=prompts --data=./content.json --slug=typography-v02
+creght content update --site_id=<project_id>/<site_id> --collection=prompts --id=<content_id> --sort=15
+```
+
+`update` applies a partial update, so `--data` is optional there — pass `--slug` / `--sort` alone to rename or reorder without re-submitting the body, as in the command above. `create` still requires `--data`.
+
+`sort` controls the order editors see in the CMS list, bigger first. Omitting it lets `create` append the entry last and leaves `update`'s current value alone. Use `content update --sort` to reorder; deleting and recreating an entry changes its id, and site versions do not snapshot CMS content, so that cannot be undone.
+
+One asymmetry worth knowing: the platform reads a zero `sort` on **create** as "auto-assign, append last", so a literal `0` cannot be created — `create --sort=0` appends. `update --sort=0` does store a real 0.
+
 ## Manage Forms
 
 List, create, update, and delete forms:
@@ -484,7 +490,11 @@ creght table record delete --site_id=<project_id>/<site_id> --table=appointments
 ```
 
 `record update` sends a patch body to the backend. Existing fields are merged,
-and a `null` field value removes that field.
+and a `null` field value removes that field. Both `create` and `update` accept
+`--sort=<n>`; omitting the flag leaves `sort` out of the request instead of
+zeroing it. Unlike content, a record's `sort` cannot be set to `0` — the platform
+ignores a zero sort on record update, so `--sort=0` is rejected there rather than
+silently doing nothing, and on `create` it means "append last".
 
 ## Func Backend Code As Files
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "creght-cli",
-  "version": "0.7.4",
+  "version": "0.7.6",
   "description": "Creght CLI for syncing local site code with Creght.",
   "license": "MIT",
   "homepage": "https://github.com/creght-dev/creght-cli#readme",