Skip to content

Response schema drift batch (spotClearinghouseState, outcomeMeta, settledOutcome, subAccounts2, legalCheck) #103

Description

@joeblau

Problem

Batch of smaller response-schema drift items (upstream nktkas#176, nktkas#180, nktkas#182, nktkas#184, nktkas#185):

  • spotClearinghouseState (src/api/info/_methods/spotClearinghouseState.ts:111): missing tokenToPortfolioSupplyRatio; outcome-market coin widened to `${number}` | `o${number}` where oN is a settled outcome.
  • outcomeMeta: missing optional deployer.
  • settledOutcome: missing optional spec.deployer and question.
  • subAccounts2: missing optional abstraction.
  • legalCheck (legalCheck.ts:37): restrictions is optional "n" | "a" with an unconfirmed-meaning FIXME; upstream made it required and widened to "n" | "a" | "o" | "u".

Fix

Apply the five schema updates, resolve the legalCheck FIXME from the upstream schema, add tests.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    api-syncSync with latest Hyperliquid API surface/schemas

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions