Description

Adds Predict live sports and extended-market support for additional basketball, baseball, hockey, soccer, and tennis leagues. This expands league parsing and supported flag filtering so newly enabled Polymarket game events can render as game detail experiences instead of generic markets.

This also fixes several extended sports details issues found while validating the new leagues:

• Parses WNBA, MLB, NHL, ATP, WTA, and ITF game slugs and tennis provider metadata.
• Uses tennis series and team metadata when ATP/WTA/ITF events only include generic tennis tags.
• Keeps extended game charts on the primary moneyline outcome so World Cup and other draw-capable markets load correctly.
• Opens extended market cards through the bottom-sheet buy flow instead of the legacy full-screen buy preview.
• Adds loading-only chart height reservation to avoid the game details footer jumping while the chart loads.
• Adds tennis market labels and separates tennis cards into Game Lines and 1st Set groups.
• Aligns footer and card outcome labels, order, and team colors for tennis moneyline and first-set winner markets.

Changelog

CHANGELOG entry: Added support for additional Predict sports leagues and extended sports market details.

Related issues

Fixes: PRED-925 https://consensyssoftware.atlassian.net/browse/PRED-925

Manual testing steps

Feature: Predict extended sports markets for newly supported leagues

  Scenario: user opens supported game detail markets
    Given Predict live sports is enabled for WNBA, MLB, NHL, ATP, WTA, and ITF
    And Predict extended sports markets is enabled for NBA, WNBA, MLB, NHL, World Cup, UCL, EPL, La Liga, Serie A, Bundesliga, MLS, FIFA Friendlies, ATP, WTA, and ITF

    When the user opens a supported game market
    Then the market renders as a game details view
    And the chart loads from the primary moneyline market
    And the footer prices match the primary moneyline outcomes

  Scenario: user opens an ATP, WTA, or ITF tennis game
    Given the event has generic Tennis and Games tags
    And the event has ATP, WTA, or ITF league metadata in series or teams

    When the user opens the game details view
    Then the event is parsed into the correct tennis league
    And the tabs show Game Lines and 1st Set
    And tennis market cards show translated labels
    And the 1st Set Winner buttons use the same team colors as the footer

  Scenario: user selects an extended sports market card
    Given the extended sports market cards are visible

    When the user taps a card outcome
    Then the bottom-sheet buy flow opens for that outcome
    And the app does not navigate to the legacy full-screen buy preview

Automated testing

• node .yarn/releases/yarn-4.14.1.cjs jest app/components/UI/Predict/utils/gameParser.test.ts app/components/UI/Predict/constants/sports.test.ts app/components/UI/Predict/providers/polymarket/utils.test.ts app/components/UI/Predict/components/PredictActionButtons/PredictActionButtons.test.tsx app/components/UI/Predict/components/PredictGameChart/PredictGameChart.test.tsx app/components/UI/Predict/components/PredictGameChart/PredictGameChart.wrapper.test.tsx app/components/UI/Predict/components/PredictGameDetailsContent/PredictGameDetailsTabsContent.test.tsx app/components/UI/Predict/components/PredictGameDetailsContent/PredictGameOutcomesTab.test.tsx app/components/UI/Predict/components/PredictMarketSportCard/PredictMarketSportCard.test.tsx
  • 9 test suites passed
  • 288 tests passed
• node .yarn/releases/yarn-4.14.1.cjs lint:tsc

Screenshots/Recordings

Before

N/A - no recordings attached in this local PR draft.

After

N/A - no recordings attached in this local PR draft.

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • N/A - no Android-specific or performance-sensitive native path changed.
• I've tested with a power user scenario
  • N/A - Predict sports details rendering does not depend on imported wallet size.
• I've instrumented key operations with Sentry traces for production performance metrics
  • N/A - no new production performance operation was added.

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.