[andy-stark-redis]

Summary

DOC-7267 items 4 and 6. Everything is checked against node-redis 6.3.1.

node_redis: 344 of 474 entries change.

• 325 signatures. 312 used the uppercase command as the method (APPEND, and for modules the dotted BF.ADD, JSON.SET, TS.ADD, which can't be called as written). 13 were the internal parseCommand(parser, ...) form. They are now the camelCase method from the package's own index.ts (append, aclCat), and module commands are client.<namespace>.<method> (client.bf.add, client.json.set, client.ft.search, client.ts.add), matching the one entry that already used client.ft.hybrid. The parser parameter is dropped from the 13, in the signature and in params.
• 226 return types. 182 of the 226 Any returns now carry the transformReply type from the source (the RESP2 form where a command declares both). 44 Promise<...> types lose the wrapper and keep their inner type.
• Parameter text and descriptions are untouched, including the 84 uppercase entries that had hand-written descriptions.

go-redis: 4 entries. The HOTKEYS entries now list ctx in params, like the other 548. (The ticket overstated this; only these four were inconsistent.)

The merged data/command-api-mapping.json is regenerated and equals the per-command data. Its only semantic changes are those node_redis and go-redis entries; no other client changed.

How to review

• All 458 resolved entries name a member in the 6.3.1 declarations, and a tsc --strict compile of typeof client.<name> succeeds for all 448 distinct names. This closes the DOC-7263 gap that tsc wasn't available. The remaining names are client-level methods (quit, select, ...) that aren't in the command map.
• Return types come from the TypeScript source, not the .d.ts, which expands aliases into unreadable types (ArrayReply<BlobStringReply<string>>, a 400-character AclUser).
• A full old-to-new report for all 344 entries is in the commit's data diff; every changed line is a signature or returns.type, except the 13 removed parser params.

Left for the rest of DOC-7267

• 44 Any returns whose source has no readable reply type (arrow functions with an inferred return): BZMPOP, BZPOPMAX, BZPOPMIN, GEODIST, GEOPOS, HSCAN, SCAN, SSCAN, ZSCAN, JSON.GET, JSON.MGET, JSON.ARRPOP, TS.GET, TS.INFO, TS.MGET, TS.MRANGE, TS.MREVRANGE, TS.RANGE, TS.REVRANGE, TS.DECRBY, the V* vector set commands, the X* stream commands, ZADD, ZINCRBY, ZMPOP, ZPOPMAX, ZPOPMIN, ZRANGE, ZRANGEBYSCORE, ZSCORE, SORT_RO, GEORADIUS_RO and GEORADIUSBYMEMBER_RO.
• 43 entries whose parameters disagree with the source. Some are real drift (CF.LOADCHUNK calls a parameter data where the source says chunk; CMS.INITBYDIM and CMS.INITBYPROB omit options; TDIGEST.* rank commands), some are my reader's limits on rest or overloaded parameters (ARGREP, EVAL*, ZRANGE). Listed: ARGREP, CF.INSERT, CF.INSERTNX, CF.LOADCHUNK, CMS.INITBYDIM, CMS.INITBYPROB, CONFIG SET, EVAL, EVAL_RO, EVALSHA, EVALSHA_RO, FCALL, FCALL_RO, FT.ALTER, FT.CURSOR READ, FT.DICTADD, FT.DICTDEL, FT.SYNUPDATE, GEORADIUS, GEORADIUS_RO, GEORADIUSBYMEMBER_RO, HSET, JSON.MGET, MIGRATE, PEXPIRE, PEXPIREAT, SORT_RO, TDIGEST.BYRANK, TDIGEST.BYREVRANK, TDIGEST.MERGE, TDIGEST.RANK, TDIGEST.REVRANK, TDIGEST.TRIMMED_MEAN, TOUCH, TS.DECRBY, TS.INCRBY, TS.RANGE, TS.REVRANGE, XADD, ZRANGE, ZRANGEBYSCORE.
• 16 entries that don't map to a command-map member and were not touched: FAILOVER, MONITOR, QUIT, RESET, SELECT, SAVE, SHUTDOWN, READWRITE, FT.PROFILE, and the pub/sub commands (SUBSCRIBE, PSUBSCRIBE, SSUBSCRIBE, UNSUBSCRIBE, PUNSUBSCRIBE, SUNSUBSCRIBE) plus CLIENT TRACKING, whose names are generic type fragments (false>, boolean>).
• Two swapped pairs: DECR.json holds the DECRBY entry and DECRBY.json holds DECR, and the same for INCR and INCRBY. They now read decrBy/decr/incrBy/incr but still sit in each other's files. Swapping them is a data move, so I left it for a decision.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation and JSON mapping metadata only; no runtime code or security-sensitive paths.

Overview
Updates the command API mapping metadata so node_redis entries reflect how callers actually invoke node-redis 6.3.1, not internal parser shapes or uppercase command literals.

Signatures move to camelCase client methods (e.g. append, clusterAddSlots) and module commands use client.<module>.<method> (e.g. client.bf.add, client.ft.search). Entries that previously documented parseCommand(parser, …) now show the public API and drop the parser parameter. Return types replace broad Any and Promise<…> wrappers with reply types taken from the client source (NumberReply, BlobStringReply, ReplyUnion, etc.).

Separately, go-redis HOTKEYS mappings add the missing ctx context.Context parameter so they match the rest of that client’s entries.

These are documentation/data-only changes to data/command-api-mapping/; no Redis client libraries or server behavior change.

^{Reviewed by Cursor Bugbot for commit 95e83a0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

🧠 Redis Memory

Found 5 related items from repository history (5 new this commit):

• Commit — DOC-7267 Make node_redis entries callable and typed, and add ctx to go-redis HOTKEYS 🆕

  DOC-7267 Make node_redis entries callable and typed, and add ctx to go-redis HOTKEYS

• PR — DOC-7267 Fix malformed and non-callable redis_py entries 🆕

  Summary

• PR — DOC-7263 Fill missing client signatures in the command-API mapping 🆕

  Summary

• Commit — DOC-7267 Fix malformed and non-callable redis_py entries 🆕

  DOC-7267 Fix malformed and non-callable redis_py entries

• Commit — DOC-7267 Fix malformed and non-callable redis_py entries 🆕

  DOC-7267 Fix malformed and non-callable redis_py entries

Memory updated at 95e83a0

[github-actions]

DOC-7267