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
Hello. I've recently upgraded to ioredis v5 and mentioned that many types are no longer exported or exported incorectly from the library. For example, I'm using NestJS for the backend and I don't like to make 3rd party library calls directly. Instead I prefer to wrap those calls into a separate injectable class so that there only will be a single instance of redis client for my app. And it's easier to test stuff by to mocking a class instead of 3rd party library calls. Previously I had a following method:
Hello. I've recently upgraded to ioredis v5 and mentioned that many types are no longer exported or exported incorectly from the library. For example, I'm using NestJS for the backend and I don't like to make 3rd party library calls directly. Instead I prefer to wrap those calls into a separate injectable class so that there only will be a single instance of redis client for my app. And it's easier to test stuff by to mocking a class instead of 3rd party library calls. Previously I had a following method:
I was using
Redis.KeyType
andRedis.ValueType
which are no longer exported from the library but are actually still defined in the source code.Also
redis.pipeline()
call was returningRedis.Pipeline
type which now is calledChainableCommander
, but when I'm switching fromto
VSCode auto-imports it from
ioredis/built/utils/RedisCommander
which really looks ugly.Is there a way to make new typings to act like those from
@types/ioredis
?The text was updated successfully, but these errors were encountered: