Handle subscription list and detail cache invalidation
DutchBen opened this issue · comments
The shape of websocket has changed slightly to make it easier for RTK to handle. One message will only contain a single cache invalidation. The updates shape means it can be passed to RTK directly without modification:
For a general cache:
{"name":"invalidateCache","value":{"type":"processes"}}
For a specific cache:
{"name":"invalidateCache","value":{"type":"processes","id":"2a953ab1-6bf1-4f67-806e-e332ba04ca6e"}}
This ticket is for implementing this new shape