perf: client-side API response cache (STY-96 step 1) - #15
Merged
Conversation
Frontend (delegated to agent frontend): - fetchJsonCached helper with 60s TTL in-memory cache (Map) - getCategories & getNews use cache; only successful responses cached - Key per URL (unique per query/category) - clearCache(pattern?) for invalidation - Aim: subsequent visits render instantly instead of waiting for API Verified: svelte-check 0 errors, lint pass, build ok.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 1 of LCP/FCP improvement: cache API responses client-side.\n\n- fetchJsonCached with 60s TTL\n- getCategories/getNews use cache (successful only)\n- clearCache(pattern?) export\n\nJANGAN DI-MERGE dulu — menunggu test ulang LCP oleh manager.