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
When using custom cache keys the cache records written as a result of an incremental response do not use the correct parent entity cache key and instead default to the behaviour as if no custom cache key was provided.
Here is incremental cache data when not using a custom cache key
And here is cache data when using a custom cache key during incremental responses. Note how the incremental responses end up using the list index ("QUERY_ROOT.allProducts.X") as the key for the record instead of the custom cache key derived key. This incorrectly breaks the cache record into two parts and makes the incremental cache records irretrievable because they're not linked by "QUERY_ROOT".
When using custom cache keys the cache records written as a result of an incremental response do not use the correct parent entity cache key and instead default to the behaviour as if no custom cache key was provided.
Here is incremental cache data when not using a custom cache key
And here is cache data when using a custom cache key during incremental responses. Note how the incremental responses end up using the list index (
"QUERY_ROOT.allProducts.X"
) as the key for the record instead of the custom cache key derived key. This incorrectly breaks the cache record into two parts and makes the incremental cache records irretrievable because they're not linked by"QUERY_ROOT"
.The text was updated successfully, but these errors were encountered: