Skip to content

fix(PM-6776): display all challenge prizes and group repeated placements - #2651

Merged
jmgasper merged 1 commit into
devfrom
fix/PM-6776-prize-display
Nov 18, 2026
Merged

jmgasper merged 1 commit into
devfrom
fix/PM-6776-prize-display

Conversation

@jmgasper

@jmgasper jmgasper commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

Challenges with more than ten placement prizes currently omit every prize after tenth place. This change renders every placement in the challenge detail header and follows both Figma layouts in PM-6776.

  • Keep the top three prizes separate; combine consecutive lower placements with equal amounts and reward types into ranges such as 4–18. Preserve source placement numbers and never merge across missing prizes or different reward types.
  • Wrap distinct prizes into additional rows and let the prize card and header grow. Use the Figma medal artwork, spacing, and dynamic placement numbers beyond tenth place; load Figtree Black for those numbers.
  • Keep checkpoint prizes, fun-challenge messaging, and registration/submission actions intact.

Design references: Repeated prizes, distinct prizes.

Validation:

  • TypeScript tsc --noEmit and ESLint on changed TypeScript files pass.
  • Browser checks render the actual header with synthetic challenge fixtures: repeated/distinct prizes × POINT/USD × 1440/1000/390/320px (16 cases). All placements and assets appear, no horizontal overflow, and submit/unregister callbacks work. Desktop card sizes match Figma at 384×256 and 384×371.
  • All 269 tests pass across the detail header, prize utilities, opportunity list card, and challenge-details flows. Regression tests cover 18 distinct prizes, repeated ranges, 25 prizes, mixed reward types, and invalid/missing placements.

The production challenge API returned HTTP 403 from this environment, so browser validation used fixtures matching the Jira/Figma cases. No AWS resource changes are required.

@jmgasper
jmgasper requested a review from kkartunov as a code owner November 18, 2026 20:15
@jmgasper
jmgasper merged commit 40c321d into dev Nov 18, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant