aleleba/lightcraft
1
0
Fork 0
mirror of https://github.com/storytold/lightcraft.git synced 2026-10-24 10:09:01 -06:00
Code Issues Packages Projects Releases Wiki Activity

Web: docs say JSON null params mean {} as empty text does

Browse Source
This commit is contained in:
Bruno-Alumn
2026-10-21 11:58:06 +00:00
parent 79f11e098c
commit a136fb5bb1
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/web.md
+4 -3
View File
@@ -151,9 +151,10 @@ are the same in every version, so serve them with `Cache-Control: no-cache` (not
`write` service hands each file to the browser as a download instead of writing it to disk.
- **Automation.** `await lightcraft.command("library.info", "{}")` runs any engine or UI command
by id on the next frame and resolves to the JSON result (`web.stats` reports storage, workers
and the render queue). The params are a JSON object (empty text means `{}`); text that isn't
one rejects the promise and runs nothing, as the control channel and MCP do, so a typo can't
run a command on the selection. This is how the headless-Chrome checks drive the page.
and the render queue). The params are a JSON object; empty text and JSON `null` mean `{}`
(no params: a command that takes photo ids then acts on the selection). Any other text that
isn't an object rejects the promise and runs nothing, as the control channel and MCP do, so a
typo can't run a command on the selection. This is how the headless-Chrome checks drive the page.
## Not yet