Engine: the name commands leave GridCraft's data names alone

`formulas.defineName {"name": "_gc_macro_1_0"}` replaced the hidden
chunk of a stored item with a visible name: the item vanished from
`stash::get` and `stash::keys`, and its other chunks stayed behind as
orphan hidden names. `formulas.deleteName` could remove chunks the
same way, and `formulas.createFromSelection` with `replace` could
replace one from a cell label. `stash::set` refused a clash with a
visible name, but nothing guarded the other direction.

Defining, renaming or deleting a name that `stash::item_key`
recognises (`_gc_<key>_<n>` and legacy `_sc_<key>`) is now refused
with an error that names `force: true`, which lets the call go ahead.
Create from Selection lists such labels in `skipped` unless `force`
is true. The params docs of the three commands say so.
This commit is contained in:
prxnvt committed 2026-10-24 01:04:51 -04:00
1 parent b90710794a
commit 4668fc30ae
3 files changed
+75 -5

No files matched your search

+2
View File
@@ -85,6 +85,8 @@ Actions made of many commands (macros, a debugger that runs one step per call) u
U+FDD0 and four hex digits, as is U+FDD0 itself, and read back as they were. `stash::items`
and `stash::keys` list the items under a key prefix in one pass over the names, at most
10,000 of them (`stash::MAX_ITEMS`). The older single-name `_sc_<key>` items are read as well.
`formulas.defineName` and `formulas.deleteName` refuse names of either shape, and
`formulas.createFromSelection` skips labels of either shape, unless `force: true` is passed.
## Agent control