fix: add support for legacy mode #455
Open
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
The latest release checks for Redis v4 but doesn't check if the user enabled legacyMode. If legacyMode is enabled, subscribe functions are causing errors. Unfortunately the Redis client API currently doesn't offer any way to check if legacy mode is enabled which is the reason why it I have to check it in this hacky way.
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.
The latest release checks for Redis v4 but doesn't check if the
user enabled legacyMode. If legacyMode is enabled, subscribe functions
are causing errors.
Unfortunately the Redis client API currently doesn't offer any way to
check if legacy mode is enabled which is the reason why it I have to
check it in this hacky way.