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
Currently, when using multiple key fields, they are concatenated without a separator in the cache key, which can lead to collisions, e.g. with extend type User @typePolicy(keyFields: "firstName lastName") both users ann acorn and anna corn will have the same key User:annacorn.
Let's use + as a separator, and escape it in the values (see discussion).
Note: this is a breaking change - meaning any existing cache keys with more than 1 key field will become invalid after this change.
The text was updated successfully, but these errors were encountered:
Currently, when using multiple key fields, they are concatenated without a separator in the cache key, which can lead to collisions, e.g. with
extend type User @typePolicy(keyFields: "firstName lastName")
both users ann acorn and anna corn will have the same keyUser:annacorn
.Let's use
+
as a separator, and escape it in the values (see discussion).Note: this is a breaking change - meaning any existing cache keys with more than 1 key field will become invalid after this change.
The text was updated successfully, but these errors were encountered: