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
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -293,6 +293,7 @@ The Node Redis client class is an Nodejs EventEmitter and it emits an event each
293
293
|`error`| An error has occurred—usually a network issue such as "Socket closed unexpectedly" |`(error: Error)`|
294
294
|`reconnecting`| Client is trying to reconnect to the server |_No arguments_|
295
295
|`sharded-channel-moved`| See [here](https://github.com/redis/node-redis/blob/master/docs/pub-sub.md#sharded-channel-moved-event)| See [here](https://github.com/redis/node-redis/blob/master/docs/pub-sub.md#sharded-channel-moved-event)|
296
+
|`invalidate`| Client Tracking is on with `emitInvalidate` and a key is invalidated |`(key: RedisItem \| null)`|
296
297
297
298
> :warning: You **MUST** listen to `error` events. If a client doesn't have at least one `error` listener registered and
298
299
> an `error` occurs, that error will be thrown and the Node.js process will exit. See the [ > `EventEmitter` docs](https://nodejs.org/api/events.html#events_error_events) for more details.
* Tag to append to library name that is sent to the Redis server
146
146
*/
147
147
clientInfoTag?: string;
148
+
/**
149
+
* When set to true, client tracking is turned on and the client emits `invalidate` events when it receives invalidation messages from the redis server.
150
+
* Mutually exclusive with `clientSideCache` option.
151
+
*/
152
+
emitInvalidate?: boolean;
148
153
/**
149
154
* Controls how the client handles Redis Enterprise maintenance push notifications.
150
155
*
@@ -525,6 +530,19 @@ export default class RedisClient<
0 commit comments