BREAKING: simplify RedisReply type, add parseReply option to Redis#sendCommand
#389
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
uki00a
changed the title
RedisReply typeRedisReply type, add parseReply option to Connection#sendCommand
uki00a
changed the title
RedisReply type, add parseReply option to Connection#sendCommandRedisReply type, add parseReply option to Redis#sendCommand
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm looking for a flexible way to handle replies to support RESP3. For this purpose, I introduced the
RedisReplytype. However, I now believe this was a premature abstraction. This PR introduces a simpler method.