refactor: use standardized redis uri for dialer arguments #42
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
|
Also uses the newer import path for redigo as described in #40 |
This was referenced Jun 28, 2018
Open
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.
Use standardized redis uri for the connection string ( implemented by DialURL in the redigo library) - as compared to specifying username / password etc.
More at - https://www.iana.org/assignments/uri-schemes/prov/redis.
Important this does break backward compatibility to be the unitary form of creating redispool.
Feel free to let me know otherwise, if it needs to be overloaded and backward compatibility is important.