dotCooCoo 74863fa778 Engine: execute refuses keys a command doesn't name, in every build ...

Session::execute ran check_params only in the engine's own tests, so a
direct execute in a release build ran a misspelled key with the
command's default. It now checks every call, the commands a command runs
included, as MCP and the control port already did. A command.batch or
an action.batch is checked before its first step runs, and each step is
checked again as it runs, so an effect.setParams step is checked
against the effects the steps before it added.

Saved steps play through Session::replay, which takes keys a command no
longer reads, so an action recorded by an older version still plays and
Session::replay still plays an older journal. The Actions panel's Play
(Accelerated, Step by Step and Pause For, its function keys and
ui.action.play) and the Batch dialog use it.

Docs: the cmd/params.rs module doc, the Parameter keys section of
docs/mcp.md and a line in docs/target-app-parity.md describe both
paths.

2026-11-08 11:22:28 +07:00

..

examples

Render: a long dashed stroke is outlined only near the view after an edit

2026-11-05 03:55:48 +07:00

src

Engine: execute refuses keys a command doesn't name, in every build

2026-11-08 11:22:28 +07:00

tests

Engine: execute refuses keys a command doesn't name, in every build

2026-11-08 11:22:28 +07:00

Cargo.toml

…