mirror of
https://github.com/jcreek/LivingDexTracker.git
synced 2026-09-18 19:42:04 +00:00
Josh Creek
c917bba54a
Since the grid transport change, opening a Pokémon fetched /api/pokedexes/[id]/entries/[entryId]. That request re-scanned the whole dex to authorise one entry, on top of an auth call and an ownership query, and production runs its functions in a different region from the database — so each card took seconds to fill in. The page's 60-second reconcile also wiped the detail cache, making cards refetch about once a minute. Details are catalog text plus personal notes, so the dex is now read once per account/dex in the background at the interactive/idle boundary and fills that cache; a card opens straight from memory. That read reuses the existing combined-data endpoint, which gains an opt-out for its count query since a caller taking every row already knows the total. The per-entry endpoint stays as the fallback for a card opened before the background read lands, and now checks membership for the single entry instead of materialising the dex. Catch status still comes from the live grid row and any queued write, so a cached detail cannot show stale progress. The packed grid transport and virtualised rendering are unchanged.
26 lines
991 B
Gherkin
26 lines
991 B
Gherkin
Feature: Signed-in page speed
|
|
As a trainer
|
|
I want my Pokédexes to open and switch quickly
|
|
So that tracking catches never feels sluggish
|
|
|
|
Lighthouse CI covers the public pages; these budgets cover the signed-in ones it can't reach.
|
|
|
|
Background:
|
|
Given I am signed in
|
|
And I have a Living Dex named "Speed Check"
|
|
|
|
Scenario: A Pokédex opens without a second round trip for its entries
|
|
When I load the Pokédex page directly
|
|
Then its entries appear within 5 seconds
|
|
And the browser did not request the grid separately
|
|
|
|
Scenario: A Pokémon's card opens from data the browser already has
|
|
When I load the Pokédex page directly
|
|
And the Pokédex has finished loading its details in the background
|
|
And I open the first Pokémon
|
|
Then its details were already in the browser
|
|
|
|
Scenario: Moving between my Pokédex list and a Pokédex is quick
|
|
When I switch between my Pokédex list and the Pokédex
|
|
Then each switch finishes within 3 seconds
|