Skip to content

Spec drift: hyperliquid — HyperliquidRawQuestion missing description field used by normalizer #529

@realfishsam

Description

@realfishsam

Summary

The HyperliquidRawQuestion type in core/src/exchanges/hyperliquid/ does not include a description field, but the Hyperliquid normalizer reads question.description to populate the PMXT market description. The type is incorrect and any TypeScript strict-mode access of .description on this type will error.

Impact

MEDIUM — market descriptions will be undefined for all Hyperliquid markets if the normalizer is reading from an untyped property. Under TypeScript strict mode this is a type error. In production it means empty descriptions.

Details

  • Type: HyperliquidRawQuestion (in core/src/exchanges/hyperliquid/)
  • Missing field: description?: string
  • Hyperliquid API does include a description string in the asset metadata response
  • The normalizer accesses .description but the type doesn't declare it, so the property is implicitly any or causes a compile error

Required Fix

Add description?: string to the HyperliquidRawQuestion interface/type in the Hyperliquid type definitions. Confirm the field name matches what the API actually returns (may be description, assetDescription, or similar).

Metadata

Metadata

Assignees

No one assigned

    Labels

    spec-driftCached OpenAPI spec out of date vs venue's live docs

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions