Feat/response caching utility #74
Open
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.
Summary
This PR adds a ResponseCache utility class that provides simple in-memory response caching with TTL support, helping developers reduce API calls and improve application performance.
Problem
Gradient API calls can be expensive and slow, especially when the same data is requested repeatedly. Developers currently have no built-in way to cache API responses, leading to:
Solution
Add ResponseCache class with:
Key Features
Testing
Added comprehensive test suite covering:
Basic cache operations (set/get)
TTL expiration behavior
Cache size limits and LRU eviction
Parameter-based caching
Cache clearing functionality
All tests pass with full coverage of cache functionality.
Usage Examples