Description

Adds a React Query (useInfiniteQuery) market-list hook, usePredictMarketList, for the redesigned Predict homepage sections and generic feed screens (epic PRED-834 — IA & Navigation Overhaul).

Reason for the change: the existing usePredictMarketData hook fetches with local useState/useEffect, a hand-rolled retry loop, manual cursor tracking, and manual dedupe. The redesigned feed is built on the generic, category-free PredictController.listMarkets API (added previously), and needs a data hook that is declarative, cache-backed, and reusable across many sections driven only by params.

Solution: a new hook built on useInfiniteQuery that:

• Calls PredictController.listMarkets (not the category-based getMarkets).
• Supports cursor pagination via the response nextCursor (getNextPageParam).
• Flattens pages and applies the existing feed hygiene: filterStandaloneMarkets, cross-page dedupe by id, and getVisiblePredictMarkets.
• Exposes React Query states (isLoading, isFetching, isFetchingNextPage, error, hasNextPage) plus refetch / fetchNextPage, and an enabled option to disable fetching.
• Uses a normalized, stable query key (fixed field order; sorted tags/series; trimmed/blank search and live: false collapse to absent).

Scope / constraints:

• Additive only. The legacy usePredictMarketData (category / getMarkets) is not removed and remains the old/fallback feed path.
• Plumbing only: there is no UI consumer in this PR. Section-specific curation (Up/Down series collapsing, Live Now interleaving/window-filtering/caps) intentionally lives in the consuming section components, not in this generic hook.
• No changes to getMarkets / listMarkets server-side code.

Files:

• app/components/UI/Predict/queries/marketList.ts (new) — normalizeMarketListParams, predictMarketListKeys, predictMarketListOptions.
• app/components/UI/Predict/queries/index.ts — registered predictQueries.marketList.
• app/components/UI/Predict/hooks/usePredictMarketList.ts (new) — the hook.
• app/components/UI/Predict/queries/marketList.test.ts and app/components/UI/Predict/hooks/usePredictMarketList.test.ts (new) — tests.

Changelog

CHANGELOG entry: null

Related issues

Refs: PRED-834 (IA & Navigation Overhaul)

Manual testing steps

This is a non-UI data hook; behavior is covered by unit tests with a QueryClient wrapper (mocking PredictController.listMarkets).

Feature: usePredictMarketList data hook

  Scenario: initial load returns markets
    Given a consumer mounts the hook with enabled params
    When listMarkets resolves with a page of markets
    Then isLoading transitions from true to false
    And markets contains the visible, deduped markets

  Scenario: cursor pagination accumulates pages
    Given the first page resolves with a nextCursor
    When the consumer calls fetchNextPage
    Then listMarkets is called with afterCursor set to the prior nextCursor
    And markets contains both pages with duplicates removed by id

  Scenario: disabled hook does not fetch
    Given the hook is mounted with enabled: false
    Then listMarkets is not called
    And isLoading is false (no permanent skeleton)

  Scenario: error then recovery
    Given listMarkets rejects
    Then error is exposed as an Error
    When the consumer calls refetch and listMarkets resolves
    Then error becomes null and markets is populated

To run locally:

yarn jest app/components/UI/Predict/queries/marketList.test.ts app/components/UI/Predict/hooks/usePredictMarketList.test.ts

Result: 18 passed. yarn lint:tsc and ESLint on the changed files are clean.

Screenshots/Recordings

N/A — no UI changes in this PR (data hook only).

Before

N/A

After

N/A

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 (unit tests for the hook and query options).
• I've documented my code using JSDoc format if applicable.
• I've applied the right labels on the PR (add team-predict + no-changelog).

Performance checks (if applicable)

• I've tested on Android — N/A (no UI/runtime path exercised yet; no consumer).
• I've tested with a power user scenario — N/A (no UI consumer).
• I've instrumented key operations with Sentry traces — the underlying listMarkets controller call is already wrapped in withTrace (TraceName.PredictListMarkets); the hook adds error reporting via Logger.error.

Pre-merge reviewer checklist

• I've manually tested the PR (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.