fix(web): picker reuses the card's person-ranking prefetch #1088
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/picker-ranking-cache"
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?
Problem
Tapping "choose an existing person / choose another person" in discovery suggestions showed "Loading people…" for a long time, even though the card view had already fetched the same person-ranking data. The prefetch cache was written on card load but never read when the picker opened.
Fix
fetchCandidatePickerRowsis now cache-first: it reuses the card's person-ranking prefetch instead of re-requesting.candidateLiveRankingRequests(Map) so concurrent opens dedupe to a single network request.Verification
Scope
Frontend-only; pairs with the backend PR (fix/person-ranking-picker-latency) which removes the server-side N+1. No schema or API changes.