Releases · Azuro-protocol/sdk

export a getUse*QueryOptions function, allowing you to construct query options outside of a component — useful for prefetching, SSR, or composing with other queries.
export supporting types: GetUse*QueryOptionsProps, Use*QueryFnData
accept select field in the query prop for result transformation and re-render optimization. select receives Use*QueryFnData, query.data type is inferred from returning data from select, if it exists

Supported for:

useConditions
useGame
useGames
useSearchGames
useSports
useSportsNavigation
useNavigation
useBetFee
useBetCalculation
useBonuses
useAvailableFreebets

import { getUseSportsQueryOptions, type UseSportsQueryFnData } from '@azuro-org/sdk'

// UseSportsQueryFnData = SportData[]
const select = (data: UseSportsQueryFnData) => data[0]

const options = getUseSportsQueryOptions({
  chainId,
  isLive: false,
  query: { 
    select, 
    staleTime: 30_000,
  },
})

await queryClient.prefetchQuery(options)

// because of select, query.data type is `SportData | undefined`

New: `sortLeaguesAndCountriesByName` in `useSports`

Optional boolean prop. When true (or when start times are equal), leagues and countries are sorted alphabetically by name instead of by game start time.

useSports({ sortLeaguesAndCountriesByName: true })

New: `hidden` Field Support in Condition Watchers

useConditionState

New prop: isInitiallyHidden?: boolean — pass condition.hidden from ConditionDetailedData
New return value: isHidden — starts true for stopped secondary conditions; resets to false when a socket update arrives (condition is still alive, only temporarily stopped by the provider)

useConditionsState

Now accepts a conditions array (Pick<ConditionDetailedData, 'conditionId' | 'state' | 'hidden'>[]) as an alternative to conditionIds + initialStates
New return value: conditionsMap — Record<string, { state: ConditionState, hidden: boolean }>
hidden follows the same logic: starts from initial data, clears on any socket update

// preferred for game markets list
const { data, conditionsMap } = useConditionsState({ conditions })

// still works for betslip / ID-only scenarios
const { data, conditionsMap } = useConditionsState({ conditionIds, initialStates })

Extended Watcher Event Data

conditionWatcher events now include:

gameId, isLiveEnabled, isPrematchEnabled, isCashoutEnabled
Full outcomes[] array (previously only odds were propagated)

outcomeWatcher events now include:

turnover

ConditionData type changes:

maxConditionPayout → maxConditionPotentialLoss
maxOutcomePayout → maxOutcomePotentialLoss
Added isCashoutEnabled, outcomes[].turnover

Improved: `useBet`

New return value: isWalletReadyToSubmit — true when the account is connected, wallet client is resolved, and the appropriate client (AA or regular) is ready
UseBetProps is now exported
Submit function now uses refs for aaClient and walletClient — captures the latest value at call time instead of closing over a stale reference
Explicit guards added: throws descriptive errors if account or wallet client is missing at submit time
Chain switch for AA wallets only fires when the current chain differs from appChain
walletClient now scoped to appChain.id via useWalletClient({ chainId })

Fixed: `useBets` — Canceled Game State

isCanceled check additionally compares game state against GameState.Canceled as a double-check for edge cases.

Dependencies

@azuro-org/toolkit bumped to 6.0.2

Full Changelog: v7.0.2...v7.1.0

Assets 2

17 Mar 10:10

on47sky

v7.0.2

eff36a5

v7.0.2

fix useSports hook:

filter.maxGamesPerLeague: set default games per league limit to 1000 (as it was in previous graphql version)

Assets 2

17 Mar 10:09

on47sky

v7.0.1

62da064

v7.0.1

fix useSports:

correctly pass "games per league" limit to API
add new prop filter.maxGamesPerLeague, deprecate old filter.limit as it ambiguous

Assets 2

16 Mar 11:24

on47sky

v7.0.0

d4ae941

v7.0.0

SDK v7.0.0:

Major dependency update: Toolkit v6
New useSearchGames hook for enhanced game discovery
New useBetCalculation hook replaces useMaxBet
Full integration with Toolkit v6's REST API methods
Removed deprecated useMaxBet hook
If used tanstack/query keys of sdk hooks, they are changed (primarily, because there was a graphql url in the key, now it's chain id)
useBets is prepared to be used with REST API, that supports order history including preparing orders