unwired: report placeholder refs ({} / null) as open slots instead of cryptic serde errors #195
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A drafting author cannot hold one campaign file that both validates-so-far and reports its open slots (fieldtest cycle-0106, F4): the ref open-slot hints fire only when the 'ref' key is OMITTED (which validate then fails with 'missing field ref'), while the natural placeholders ref: {} and ref: null produce cryptic serde errors ('expected map with a single key'; 'invalid type: null, expected string or map' — the latter falsely implying a bare-string ref works) and --unwired then claims 'no open slots'.
Likely shape: open_slots_* treat an empty-object or null ref value as the open slot they already know how to report; validate keeps refusing but with the same open-slot phrasing instead of raw serde prose.