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
Hey @kennedyrs, thanks for reporting the bug. Redis driver uses promises because network I/O to Redis shouldn't block the Node.js event loop. This is not a problem for Memory driver since we can directly access the memory synchronously without blocking the event loop.
In fact, any driver written for external caches such as Redis, Memcached, etc. will have to be promises.
@masasron is it alright if I promisify all of the this.store methods? Memory driver will just resolve the promise right away (e.g. wrapped in Promise.resolve()) but it should make accessing the store much more consistent.
When using Redis, the function below returns a promise to the count variable
The text was updated successfully, but these errors were encountered: