dotCooCoo 6e6fbbac1d Commands: an unknown command id is answered with the nearest command id ...

A misspelled parameter key got a did-you-mean suggestion, but a
misspelled command id only got "unknown command `select.al`", through
the CLI, MCP and the control channel alike. Session::execute now names
the nearest command id, using the same matching as parameter keys
(ignoring case), and action.batch does the same for an unknown step. An
id with no near match keeps the plain error.

The matching skips candidates whose length differs by more than the
allowed number of edits, so a very long unknown command id or parameter
key is answered at once instead of being measured against every command
id or accepted key.

The new message has a row in every catalog, and docs/mcp.md's
Parameter keys section shows it.

2026-10-24 11:20:27 -07:00

..

src

Commands: an unknown command id is answered with the nearest command id

2026-10-24 11:20:27 -07:00

tests

Fix #3621: bound function-based shading reads per import

2026-10-24 19:27:44 +07:00

Cargo.toml

Security: file authority for stored paths, linked files, placed documents, font folders, recovery areas and atomic saves

2026-10-24 17:19:59 +07:00