chore: create root params list type

[asalsys]

Description

This PR introduces a comprehensive TypeScript type definition file (Params.ts) for navigation parameters in the MetaMask Mobile app.

Reason for the change:
Navigation in React Native apps using React Navigation benefits greatly from strong typing. Currently, route parameters are loosely typed, which can lead to runtime errors when passing incorrect or missing parameters between screens.

Improvement/Solution:

• Created app/constants/navigation/Params.ts with ~1,267 lines of type definitions
• Defines RouteParams interface that mirrors the structure of Routes.ts
• Provides 80+ individual parameter interfaces for specific routes (e.g., BrowserParams, StakeParams, BridgeParams)
• Includes utility types like GetRouteParams<T> for easy type extraction
• Exports RootStackParamList for React Navigation compatibility
• Covers all major navigation flows: Ramp, Deposit, Bridge, Perps, Predict, Staking, Earn, Card, Notifications, and more

Changelog

CHANGELOG entry: null

Related issues

Fixes: #23762

Manual testing steps

Feature: Navigation parameter types

Scenario: Developer uses typed navigation parameters
Given the developer imports types from app/constants/navigation/Params.ts

When the developer navigates to a typed route
Then TypeScript provides autocomplete for valid parameters
And TypeScript shows errors for invalid or missing required parameters## **Screenshots/Recordings**

Before

N/A - This is a new type definition file (no visual changes)

After

N/A - This is a TypeScript type file only, no runtime or visual changes

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.

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.

---

Note

Low Risk
Type-only refactor that centralizes navigation parameter definitions; risk is limited to potential TS build/type regressions or mismatched param shapes where routes are wired.

Overview
Adds a new app/core/NavigationService/types.ts that defines a flattened RootStackParamList and globally registers it with React Navigation for type-safe navigate/route params across the app.

Extracts and centralizes many route param interfaces into dedicated *.types.ts files (Bridge, Ramp, Earn, Stake, Card, Send, Modals, Multichain, etc.), and updates existing screens to export their param types (e.g., Ramp BuildQuoteParams, OrderDetailsParams, Deposit KycWebviewModalParams) and re-export webview params for compatibility. Also refactors Predict navigation to use named param interfaces instead of inline route param objects.

^{Written by Cursor Bugbot for commit 840af66. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[Cal-L]

Left some comments! We're also missing defining the global type mentioned in #23762. After defining the global namespace, you can verify that the types are picked up by checking the useNavigation hook

[Cal-L]

This is a types file and should be named types.ts. Let's also move it into the NavigationService directory

[Cal-L]

This most likely has missing items screen names since some things are hardcoded. In addition of this list, you can reference the navigation stacks to fill in the blanks.

[Cal-L]

The RootParamsList below seems to be the correct definition. RouteParams seems duplicate and can be removed

[Cal-L]

The screen params themselves should be defined in the feature directories and follow the import pattern to respect CO scopes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 92%

click to see 🤖 AI reasoning details

E2E Test Selection:
This PR introduces TypeScript type definitions for navigation parameters across the MetaMask Mobile app. The changes are purely compile-time TypeScript types with no runtime code changes:

1. New centralized types file (app/core/NavigationService/types.ts): Creates a comprehensive RootStackParamList interface that consolidates navigation parameter types from various feature modules. This provides TypeScript autocomplete and error checking for navigation but has zero runtime impact.

2. New type definition files: Multiple new .types.ts files created for various features (Bridge, Card, Earn, Ramp, AccountActions, MultichainAccounts, Modals, SendFlow, NetworkSelector, etc.) - all containing only TypeScript interfaces.

3. Minor modifications to existing files: Small changes to export existing interfaces that were previously internal (e.g., BuildQuoteParams, OrderDetailsParams, ShareAddressQRParams). These are just adding export keywords to existing type definitions.

Why no E2E tests needed:

• All changes are TypeScript type definitions only
• No runtime code is modified
• No component logic, UI rendering, or data flow changes
• No state management changes
• These are compile-time only changes for better type safety and developer experience
• The app behavior remains completely unchanged

The changes improve code maintainability and TypeScript support without affecting any user-facing functionality.

Performance Test Selection:
These changes are purely TypeScript type definitions with no runtime code changes. Type definitions are compile-time only and have zero impact on app performance - they don't affect UI rendering, data loading, state management, or any runtime behavior. No performance tests are needed.

View GitHub Actions results

No more core platform changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud