Skip to content

feat: expose sendCommand on multi for all clients - #3181

Merged
nkaradzhov merged 1 commit into
redis:masterfrom
nkaradzhov:multi-send-command
Feb 25, 2026
Merged

nkaradzhov merged 1 commit into
redis:masterfrom
nkaradzhov:multi-send-command

Conversation

@nkaradzhov

Copy link
Copy Markdown
Collaborator

This change makes sendCommand a public method on multi/pipeline for standalone client, cluster, sentinel, and pool.

Note: Using sendCommand breaks the type inference for execTyped and execAsPipelineTyped. It is possible to fix this by modifying InternalRedisClientMultiCommandType, but this significantly hinders TypeScript performance and is unfeasible for now.

fixes #3172

Description

Describe your pull request here


Checklist

  • Does npm test pass with this change (including linting)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

This change makes sendCommand a public method on multi/pipeline for
standalone client, cluster, sentinel, and pool.

Note: Using sendCommand breaks the type inference for execTyped and
execAsPipelineTyped. It is possible to fix this by modifying
InternalRedisClientMultiCommandType, but this significantly hinders
TypeScript performance and is unfeasible for now.

fixes redis#3172

@PavelPashov PavelPashov left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nkaradzhov
nkaradzhov merged commit ccf84f2 into redis:master Feb 25, 2026
15 checks passed
@nkaradzhov
nkaradzhov deleted the multi-send-command branch February 25, 2026 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement sendCommand inside multi context

2 participants