fimo 2.10.0-staging.5 → 2.10.0-staging.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/skills/fimo-cli/references/assets.md +2 -0
- package/assets/skills/fimo-cli/references/content.md +11 -1
- package/assets/skills/fimo-code/references/content/richtext.md +2 -2
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +25 -15
- package/package.json +8 -8
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
|
@@ -15,6 +15,8 @@ fimo assets upload ./hero.jpg --name "Hero Image" --parent-id "<folder-uuid>"
|
|
|
15
15
|
fimo assets upload ./screenshot.png --folder-path ".agents/<session-id>/screenshots"
|
|
16
16
|
```
|
|
17
17
|
|
|
18
|
+
Upload options are `--name`, `--parent-id`, and `--folder-path`. Set alt text in the content media field's `alt` value or the rendering component; upload does not accept `--alt`.
|
|
19
|
+
|
|
18
20
|
Response (JSON) — the full asset object, wrapped in a `data` envelope:
|
|
19
21
|
|
|
20
22
|
```json
|
|
@@ -81,7 +81,17 @@ fimo entries bulk-update <TypeName> (--file <path> | --stdin)
|
|
|
81
81
|
fimo entries bulk-delete <TypeName> (--ids <id1>,<id2> | --where '<json>') [--locale es]
|
|
82
82
|
```
|
|
83
83
|
|
|
84
|
-
|
|
84
|
+
`create` and `update` require `--body` with a `data` envelope. The content type is positional. For JSON files, use `bulk-create` or `bulk-update` with their documented array formats.
|
|
85
|
+
|
|
86
|
+
```bash
|
|
87
|
+
fimo entries create BlogPost --body '{"data":{"slug":"hello","title":"Hello"}}'
|
|
88
|
+
fimo entries update BlogPost <id> --body '{"data":{"title":"Updated"}}'
|
|
89
|
+
fimo entries list BlogPost --where '{"slug":"hello"}'
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
For `get`, `update`, and `delete`, use the UUID returned as `id` by create/list. To find an entry by slug, filter with `list --where` as above, then use its `id`.
|
|
93
|
+
|
|
94
|
+
Run `fimo skills get fimo-code --ref content/richtext` before constructing an entry payload: slug belongs inside `data`, media has a specific shape, and richtext must be Tiptap JSONContent.
|
|
85
95
|
|
|
86
96
|
`entries list` accepts the same read query surface as generated hooks:
|
|
87
97
|
|
|
@@ -33,7 +33,7 @@ generated client hydration helper where required.
|
|
|
33
33
|
|
|
34
34
|
## Entry payload
|
|
35
35
|
|
|
36
|
-
|
|
36
|
+
`entries create` and `entries update` take `--body` with every field, including the collection slug, under `data`:
|
|
37
37
|
|
|
38
38
|
```json
|
|
39
39
|
{
|
|
@@ -46,7 +46,7 @@ CLI entry writes put every value, including the collection slug, under `data`:
|
|
|
46
46
|
}
|
|
47
47
|
```
|
|
48
48
|
|
|
49
|
-
|
|
49
|
+
Keep `slug` inside `data`; `entries create` rejects unsupported top-level keys.
|
|
50
50
|
|
|
51
51
|
Slugs should be lowercase, hyphenated, stable, meaningful, and unique per content type. Fimo slugifies the supplied candidate. If omitted, Fimo generates one, which is unsuitable for content with durable public URLs.
|
|
52
52
|
|