Per-call batch: false for ENS actions (getEnsText, getEnsAddress, …)

[Rinse12]

Description

Client-level batch.multicall can be bypassed per-call in call / readContract: the call action reads batch = Boolean(client.batch?.multicall) from its arguments, so passing batch: false on a single call skips the multicall scheduler and sends a standalone eth_call.

However, the ENS actions (getEnsText, getEnsAddress, getEnsName, getEnsResolver) construct their readContractParameters object explicitly and only forward blockNumber / blockTag:

https://github.com/wevm/viem/blob/main/src/actions/ens/getEnsText.ts

const readContractParameters = {
  address: universalResolverAddress,
  abi: universalResolverResolveAbi,
  args: [...],
  functionName: 'resolveWithGateways',
  blockNumber,
  blockTag,
} as const

So on a client created with batch: { multicall: true } there is no way to opt a single ENS lookup out of batching. The only workarounds are keeping a second unbatched client, or re-implementing the universal-resolver readContract call manually.

Relatedly, ReadContractParameters doesn't include batch in its type — readContract forwards it to call at runtime via its rest spread, but TypeScript rejects it.

Proposal

• Add batch?: boolean to the ENS action parameter types and forward it into the built readContractParameters.
• Add batch?: boolean to ReadContractParameters (the runtime already forwards it; this just types the existing behavior).

Use case

We enable batch.multicall (with a wait window) on a shared PublicClient to coalesce bursts of concurrent ENS text-record lookups into one aggregate3 call. Occasionally a single latency-sensitive lookup should skip the wait window and go out immediately — today that isn't expressible through the ENS actions.

Happy to open a PR if this is welcome.