Skip to content

Refactor cache expiration to use timeout seconds param#550

Closed
StuartFerguson wants to merge 2 commits intomainfrom
task/#538_application_cache_changes
Closed

Refactor cache expiration to use timeout seconds param#550
StuartFerguson wants to merge 2 commits intomainfrom
task/#538_application_cache_changes

Conversation

@StuartFerguson
Copy link
Copy Markdown
Member

Refactored ApplicationCache and related view models to accept an integer timeout (in seconds) for cache expiration instead of requiring MemoryCacheEntryOptions. The ApplicationCache class now constructs MemoryCacheEntryOptions internally based on the provided timeout. Updated all usages and tests to pass timeout values, simplifying cache management and reducing repetitive code. SetAccessToken remains flexible, still accepting MemoryCacheEntryOptions.

closes #538

Refactored ApplicationCache and related view models to accept an integer timeout (in seconds) for cache expiration instead of requiring MemoryCacheEntryOptions. The ApplicationCache class now constructs MemoryCacheEntryOptions internally based on the provided timeout. Updated all usages and tests to pass timeout values, simplifying cache management and reducing repetitive code. SetAccessToken remains flexible, still accepting MemoryCacheEntryOptions.
@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented Apr 19, 2026

Up to standards ✅

🟢 Issues 1 minor

Results:
1 new issue

Category Results
CodeStyle 1 minor

View in Codacy

🟢 Metrics 0 complexity · -5 duplication

Metric Results
Complexity 0
Duplication -5

View in Codacy

TIP This summary will be updated as you push new changes. Give us feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Application Cache Changes

1 participant