feat: enhance auction interactions and player statistics UI

This commit is contained in:
dahyeon committed 2026-11-11 20:06:22 +09:00
1 parent 6c582ba3cf
commit be4de61bb7
115 files changed
+13292 -2871

No files matched your search

@@ -0,0 +1,92 @@
# Auction player information — applied v2
Verified 2026-11-11 on the actual auction route:
`http://localhost:5173/match/6a3b94bccb8a54219653f457/auction`.
## Approved source and implementation
The selected reference is `src/design-previews/player-information-v2/Preview.tsx`
and its CSS. Production uses the separate `AuctionPlayerProfile.tsx`, `profile.css`,
and history/statistics helpers; it imports no prototype fixtures.
The identity header, queue tabs, six position tabs, three summary metrics,
overlapping champion avatars, three performance metrics and scrolling game table
follow the approved reference. Container queries adapt the card at its actual
440 px desktop / 311 px mobile widths. The existing auction bid/status rendering,
team cards and chat are preserved.
## Browser results
- Initial player is 붕어베이글. Requested first position is 미드 and the selected
history position starts at 미드. Internal history: seven actual games, 57% wins,
2.96 aggregate KDA, 57% mean kill participation. All portraits loaded.
- Solo overall window has 20 games dated October 30–November 7. The independent
mid window includes the older October 26 game even though it is outside those
overall 20 games. Support independently has 20 games; top/ADC have one each;
jungle has zero. No missing games are invented or padded.
- Remakes remain in the game list; summary performance excludes them and states
that exclusion. The observed overall solo window has 19 completed games plus
one remake, so summary wins/losses differ intentionally from the list count.
- Support puts vision/minute first. Empty jungle shows dashes and an explicit
empty state. Queue/position changes update the sample, metrics and champions
together. No champion-count text or disclosure controls were introduced.
- The table has all 20 rows, a 228 px viewport and sticky headings. End reaches
the final row (scrollTop 565.3 of a 566 px range); changing position resets to 0.
- ArrowRight and Home move selection and focus between position tabs. Internal
game links retain the match/game route and return-to-auction state.
- At 360 px viewport, page scrollWidth is 345 px and card scrollWidth is 311 px:
no horizontal overflow. Desktop 1280 px also has no horizontal overflow.
Browser viewport override was reset; final state is 내전 / 미드.
## Evidence
- Approved source: `src/design-previews/player-information-v2/Preview.tsx`.
- Full mobile card: `C:/Users/park/.codex/visualizations/2026/11/11/01a1c930-2c9b-7531-a709-2ebb87701e9a/player-information-applied/mobile.jpg`.
- Desktop context: same directory, `desktop.jpg`.
- Desktop identity, tabs and metrics: same directory, `auction-player-card.jpg`.
## Data and validation
Both API and web TypeScript checks passed. Targeted ESLint passed. Eleven web
tests (including the five existing prototype tests) and seventeen backend tests
passed. Tests cover filtering before limiting, older position records, legacy
pagination, stalled cursors, independently capped counts, participant-scoped
Mongo predicates, averages, missing metrics and remake exclusion.
The connected staging API predates lane filtering and returns no positionCounts.
The UI therefore uses a cached compatibility collector over its paginated public
history API. It retains only the independent recent-20 windows. Once the new
backend response is deployed, the UI requests the selected position directly.
The new backend code was type/unit tested, not deployed or verified against a
live database in this task (local bootstrap credentials were unavailable).
Current history APIs use their configured season scope, shown below the card.
The staging DDragon manifest endpoint returned HTTP 500. A separate card-only
query obtains champion metadata from Riot's official CDN when that endpoint
fails. Its partial manifest does not replace the application's full manifest
cache used by item/rune views.
## Size and stable-height follow-up
- Desktop inspector width now matches the approved two-column reference:
`(1104 - 24) / 2 = 540px`. The page maximum width increases by the same 100px,
retaining the existing 484px team grid at the maximum desktop layout width.
The four-column layout starts at 1440px with minimum widths for adjacent areas.
- The passed-status footer uses the reference's 12px type and 10px vertical
padding. Before the fixed-height request, the complete internal card matched
the reference's approximately 826px height.
- The history body now reserves 656px on desktop, including the maximum solo
view, ten champion portraits, the mastery row and the 228px match list. It
reserves 720px at container widths up to 480px. Short/empty results retain the
space, and flex layout keeps the data note at the bottom. Overflow remains
available as an accessibility fallback; it is not needed in the tested states.
- Browser measurements: the full desktop card is 877.60px for internal seven
games, empty support, solo loading and solo support twenty games. On mobile,
both twenty games and empty jungle measure 957.55px. History clientHeight and
scrollHeight are equal (656 / 720 respectively); no extra body scroll appears.
- Web TypeScript and AuctionPage/profile ESLint checks passed. This CSS change
adds no new unit tests; verification exercises the real tab interactions.
- During follow-up, another local Vite process replaced port 5173's staging
configuration with development. Live-data verification continued on the
isolated port 5174 staging proxy (`tmp/auction-profile-qa.mjs`, ignored), with a
separate Vite dependency cache. No auction actions were performed.