aleleba/figcraft
1
0
Fork 0
mirror of https://github.com/storytold/figcraft.git synced 2026-11-01 14:26:49 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge main into #1143

Browse Source 
file.open and file.export docs: main's (reload, export options) plus the Penpot format.
This commit is contained in:
bflatastic
2026-10-29 13:51:11 +07:00
parent 08ac26299e c2a6b71020
commit 0a6642747a
60 changed files with 983 additions and 127 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/cli.md
+3 -1
View File
@@ -141,7 +141,9 @@ Runs commands in a headless session (a new document, or `--in`), printing one JS
```
The whole script is **one undo step**, and it is **all-or-nothing**, exactly like running the same
commands through `command.batch` (the MCP tool `batch`, the control channel, plugins). A step named
commands through `command.batch` (the MCP tool `batch`, the control channel, plugins). A step key
other than `command`, `params` and `as`, or a parameter the command's doc (`figcraft-cli commands`)
doesn't list, fails the script with an error naming it (`ids` and `id` are always taken). A step named
with `"as"` can be used by later steps: `{"$ref": "name"}` in a step's params is the `id` in that
step's result (`{"$step": n}` does the same by zero-based position), and `"field"` takes another key
or a slash path such as `ids/0`. So a step can target a layer an earlier step of the same script