refactor: simplify query combination typing

[0xAlunara]

My mind is drained after this session and I no longer wish to spend further time on this nor the convoluted typing 😭

The useQueryMapping function and corresponding combineQueriesToObject typing were all kinds of fucked up and broken anyway; straight up not working. I've tried to keep the useQueryMapping function, but trying to do so gets you into type hell.

In short, instead of using

return useQueryMapping(
  uniqueAddresses.map((tokenAddress) => getTokenUsdRateQueryOptions({ chainId, tokenAddress })),
  uniqueAddresses,
)

you can use

return useQueries({
  queries: uniqueAddresses.map((tokenAddress) => getTokenUsdRateQueryOptions({ chainId, tokenAddress })),
  combine: (results) => combineQueriesToObject(results, uniqueAddresses),
})

In the case of token queries it correctly deduces the type now as Record<string, number>, and not Record<string, any>, so you dont need these ugly hacks like

const { data: usdRatesRaw } = useTokenUsdRates({ chainId, tokenAddresses: collateralTokenAddresses })
const usdRates = useMemo(() => usdRatesRaw ?? ({} as Record<string, number>), [usdRatesRaw])

but can simply use

const { data: usdRates } = useTokenUsdRates({ chainId, tokenAddresses })

Very useful for other cases where you want to execute multiple non-batched queries and group them back into a record (like user balances, which is why I started working on this)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
curve-dapp	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 12, 2025 5:41pm
curve-dapp-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 12, 2025 5:41pm