{"version":"2.1.61","anchor":"smarter-client-data-cache-updates","canonical_anchor":"smarter-client-data-cache-updates","heading":"Smarter client data cache updates","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.61\/e\/smarter-client-data-cache-updates","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.61","markdown":"### Smarter client data cache updates\n\n**What**\n\nThe client data cache (used for fetching configuration from the API) now performs a deep equality check before updating state, avoiding unnecessary state propagation when the fetched data hasn't changed.\n\n**Details**\n\n- Previously, every fetch from the OAuth client data endpoint would overwrite the cache with a new object, even if the data was identical\n- Now uses `isDeepStrictEqual` to compare fresh data against cached data and only triggers a state update when something actually changed\n- This reduces unnecessary re-renders and state propagation in the UI\n\n**Evidence**\n\nClient data fetch function `sQK()` (search for `\"clientDataCache\"`) \u2014 added deep equality check via `$Q()` before cache write at line ~69394"}