feat(cli): record 写入 --typecast/--order/--field-key-type + 附件字段 URL 导入 skill 文档 (0.2.0)
This commit is contained in:
@@ -152,6 +152,16 @@ const res = await fetch(triggerInput._apiBaseUrl + "/api/table/tblB/record", {
|
||||
`401` = bad/expired token, `403` = scope or base-role too low.
|
||||
6. To see the exact request the CLI sends for any operation, run it with
|
||||
`--debug` (prints method/url/body) — the fastest way to learn a route.
|
||||
7. **Attachment fields accept URLs** (2026-10): pass `{"url":"https://…","name":"…"}` items
|
||||
(or a URL string with `typecast:true` — note `typecast` is a BODY key) in
|
||||
record create/update `fields`, and the backend downloads the file
|
||||
(SSRF-guarded, size-capped) into attachment storage — response items come
|
||||
back with real `token`/`presignedUrl`. A failed download rejects the whole
|
||||
request (400); nothing is silently dropped. V1 (legacy) bases need
|
||||
`typecast:true` for the string form, V2 bases accept both. The dedicated
|
||||
`POST /api/table/{tid}/record/{rid}/{fid}/uploadAttachment` (multipart,
|
||||
`file` or `fileUrl`) is the older single-record path — the plain record
|
||||
routes now cover URL imports.
|
||||
|
||||
## 5. Full Route Inventory (this guide ≠ the whole API)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user