You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems as though there is no way to test code which uses client-unsupported commands via: client.Do(ctx, "cmd", ...args)
There definitely seems to be no example and I see no Issues filed which mention it, and there is no immediately obvious way to set an expectation for an arbitrary Cmd when looking at the source code. This prevents testing of any code which uses a custom redis module to provide commands not natively supported by the redis client, which seems like a relatively common use case, so I'm wondering if this is an oversight in the documentation and example code?
The text was updated successfully, but these errors were encountered:
Given the example code for testing pipeline, I would imagine that if Do() were supported, pipelining Do() would also be supported by setting an expectation for each pipelined command.
It seems as though there is no way to test code which uses client-unsupported commands via:
client.Do(ctx, "cmd", ...args)
There definitely seems to be no example and I see no Issues filed which mention it, and there is no immediately obvious way to set an expectation for an arbitrary Cmd when looking at the source code. This prevents testing of any code which uses a custom redis module to provide commands not natively supported by the redis client, which seems like a relatively common use case, so I'm wondering if this is an oversight in the documentation and example code?
The text was updated successfully, but these errors were encountered: