Description

This PR removes all i18n dependencies (strings() calls) from core-bound Perps files to prepare for migration to @metamask/perps-controller in the core monorepo.

Why?

Core monorepo packages must be i18n-agnostic. Previously, several Perps files used strings() for translated error messages and time formatting, which created a dependency on the mobile i18n system.

What changed?

• Error handling: Validation errors now return standardized error codes (PERPS_ERROR_CODES.ORDER_SIZE_MIN) instead of translated strings
• Time formatting: Provider returns raw estimatedMinutes: number instead of formatted strings; UI hooks handle formatting
• Translation layer: The translatePerpsError.ts and perpsErrorHandler.ts files handle translating error codes to user-facing messages
• No behavior change: End users see the same error messages and time displays; they're just translated/formatted at a different layer

Files modified:

• perpsErrorCodes.ts - Added 6 new validation error codes
• HyperLiquidProvider.ts - Removed all 17 strings() calls (15 error messages + 2 time formatting)
• translatePerpsError.ts - Added mappings for new error codes
• perpsErrorHandler.ts - Added mappings for new error codes
• HyperLiquidProvider.test.ts - Updated test expectations to use error codes and raw time values
• usePerpsWithdrawQuote.ts - Added time formatting logic (moved from provider)
• usePerpsOrderValidation.ts - Added translatePerpsError for protocol validation errors
• controllers/types/index.ts - Added estimatedMinutes?: number to AssetRoute.constraints

New error codes added:

• ORDER_SIZE_POSITIVE - Order size must be positive
• ORDER_PRICE_REQUIRED - Price is required for validation
• ORDER_SIZE_MIN - Order value below minimum
• ORDER_LEVERAGE_INVALID - Leverage outside valid range
• ORDER_LEVERAGE_BELOW_POSITION - Leverage below existing position requirement
• ORDER_MAX_VALUE_EXCEEDED - Order value exceeds maximum

Changelog

CHANGELOG entry: null

Related issues

Part of: PerpsController migration to core monorepo (Stages 1 & 2 complete)

Manual testing steps

Feature: Perps validation error messages

  Scenario: User sees validation error when placing invalid order
    Given user has Perps enabled and is on the order screen

    When user enters an order size of 0
    Then user sees "Order size must be positive" error message

    When user enters a limit order without a price
    Then user sees "Limit price is required" error message

    When user enters an order below minimum value ($10)
    Then user sees "Minimum order value" error message

Feature: Withdrawal time estimate display

  Scenario: User sees estimated withdrawal time
    Given user is on the Perps withdrawal screen

    When user enters a valid withdrawal amount
    Then user sees "5 minutes" as estimated processing time

Screenshots/Recordings

N/A - No visual changes. Error messages and time displays appear identically to before.

Before

• Error messages returned via strings() calls in HyperLiquidProvider
• Time formatting done in provider with strings('time.minutes_format_plural', ...)

After

• Error messages returned as error codes from HyperLiquidProvider, translated at UI layer
• Time returned as raw estimatedMinutes: number, formatted in usePerpsWithdrawQuote hook

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.