Make return_buffers work with channel names. #354
Closed
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.
When using pub/sub, return_buffers is ignored and channel names are forced to be strings, making it impossible to use binary channel names when accessing redis using this library.
It turns out the .toString() on these names is superfluous as the underlying parser is already returning these correctly as either strings or node.js Buffer objects based on the return_buffer setting.
(I am fully willing to believe, however, that a more complex code change is needed to work with different parser backends, or in more circumstances; I know very little about this codebase in general.)
Ready to merge checklist