feat(activity): optimize API fetch strategy for immutable dates #324
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/steeper!324
Loading…
Reference in a new issue
No description provided.
Delete branch "phase07-fetch-optimization"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Add test coverage for the existing fetch optimization, completing #262.
Changes
TestGetRefreshWindowPastDatesImmutable— verifies that when past dates are all cached and today is missing,sincepoints to today (not an earlier date), preventing redundant fetches for immutable past dataisDateImmutable()+isCacheStale()prevent fetches for past dates (never stale)GetRefreshWindow()computessincefrom the earliest stale/missing day in the windowFetchActivityEvents()batches all graph types in one paginated API call#261If-Modified-Since requires HTTP-level support at the forge client layerReferences: #262, #259, #260
Testing
go test -race ./...— all passReview
Result: Approved — no blocking issues.
Summary: Tests-only PR.
TestGetRefreshWindowPastDatesImmutableverifies that when all past dates are cached and only today is missing,sincepoints to today (not earlier), preventing redundant fetches for immutable past data. ROADMAP2.md updated — #259 and #260 complete.Checklist:
go test -racepasses