diff --git a/docs/source/routing/performance/caching/entity.mdx b/docs/source/routing/performance/caching/entity.mdx index 64618ca2d5..bf2f7e6826 100644 --- a/docs/source/routing/performance/caching/entity.mdx +++ b/docs/source/routing/performance/caching/entity.mdx @@ -216,16 +216,15 @@ This entry contains an object with the `all` field to affect all subgraph reques You can invalidate entity cache entries with a [specifically formatted request](#invalidation-request-format once you [configure your router](#configuration) appropriately. For example, if price data changes before a price entity's TTL expires, you can send an invalidation request. ```mermaid - flowchart RL subgraph QueryResponse["Cache invalidation POST"] n1["{ -   "kind": "subgraph", -   "subgraph": "price", -   "type": "Price", -   "key": { -     "id": "101" -   } +     "kind": "subgraph", +     "subgraph": "price", +     "type": "Price", +     "key": { +         "id": "101" +     } }"] end @@ -236,18 +235,18 @@ flowchart RL end subgraph PriceQueryFragment["Price Query Fragment (e.g. TTL 2200)"] - n2[" ̶{̶ -   " ̶p̶r̶i̶c̶e̶": ̶{̶ -     " ̶i̶d̶": ̶1̶0̶1̶, -     " ̶p̶r̶o̶d̶u̶c̶t̶_̶i̶d̶": ̶1̶2̶, -     " ̶a̶m̶o̶u̶n̶t̶": ̶1̶5̶0̶0̶, -     "̶c̶u̶r̶r̶e̶n̶c̶y̶_̶c̶o̶d̶e̶": " ̶U̶S̶D̶" -    ̶}̶ - ̶}̶"] + n2["{ +     "price": { +         "id": 101, +         "product_id": 12, +         "amount": 1500, +         "currency_code": "USD" +     } + }"] end Router - Database[("   ")] + Database[("    ")] QueryResponse --> Router Purchases --> Router