-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nil key should also be namespaced #106
Comments
The redis ruby adapter's documentation explicitly calls out that keys should be strings, so I'm very wary of defining behaviour here where it is undefined upstream:
|
I believe this is the line where redis-rb convert the key from
for example, |
As I said earlier, I'm wary of defining behaviour based on the observed (but undefined) behaviour of private api's, but this behaviour is also surprising, which is why I left this ticket open. I'll circle back to it in the coming days, when I have time to consider all of the potential ramifications of your proposed fix (#107) and/or any alternates. That said, I'd like to address a couple of your arguments:
No, it doesn't; in yardoc (which is how the redis ruby adapter gem documents itself), the way to require an object that responds to
The documentation declares the contract of the public API for a library; in Semantic Versioning, the implementation details are free to change without a major version release (and thus an obvious warning to the consumers of a library), so long as the method behaves in the same manner from an external standpoint. The fact that version 3.2.1 of the redis ruby adapter sends |
ah I see! Thanks a lot for such a great explanation! Very clear! 👍 |
currently
nil
key is treated as empty-string key without namespace. which is confusing.The text was updated successfully, but these errors were encountered: