-
Notifications
You must be signed in to change notification settings - Fork 10
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
subscribe arguments are wrong #46
Comments
I agree, For the type to be as you suggest, we'd need In the meantime, arguments are flattened so calling Let me know if you think the library should be handling |
arguments for SUBSCRIBE were in the wrong format, which caused this bug: mmkal/handy-redis#46 this change makes them match unsubscribe: https://github.com/antirez/redis-doc/blob/c882f1d3a767a096453489b00d7ec5bcc2eceaa7/commands.json#L2997-L3010
@idris I opened a PR in redis-doc to fix this: redis/redis-doc#1229. For now, I'll keep this issue open since I would rather avoid maintaining manual overrides of the docs. |
arguments for SUBSCRIBE were in the wrong format, which caused this bug: mmkal/handy-redis#46 this change makes them match unsubscribe: https://github.com/antirez/redis-doc/blob/c882f1d3a767a096453489b00d7ec5bcc2eceaa7/commands.json#L2997-L3010
this updates both the https://github.com/antirez/redis-doc and https://github.com/NodeRedis/redis-commands dependencies. fixes #46 Mostly the changes are new commands, but some function can now be called like client.hset('myhash', ['field1', 'Hello']) rather than client.hset('myhash', 'field1', 'Hello'). This allows setting multiple fields, e.g. client.hset('myhash', ['field1', 'Hello'], ['field2', 'Goodbye']). The last arg of setbit can also now be number, rather than a string. Likely the string form will be dropped in the next major version. See the diff from the PR merging this change for examples in the snapshot tests.
🎉 This issue has been resolved in version 1.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
subscribe
inhandy-redis
is typed assubscribe(...channels: Array<[string]>): Promise<any>;
, but it should besubscribe(...channels: Array<string>): Promise<any>;
The text was updated successfully, but these errors were encountered: