refactor: use getAction internally

[holic]

As an author of custom actions and action overrides, I will use viem actions internally but sometimes forget to call them getAction so that the actions can compose on one another.

For example, maybe I'll use getChainId internally in my custom action, but I want this to be composable with an action that overrides getChainId to cache the RPC's chain ID. If I don't call this with getAction, I'll accidentally bypass this cache and viem will do the underlying RPC call.

I've seen this pattern in both in my code, other SDKs, and within viem itself.

I am curious if, instead of requiring all action authors to use getAction, that viem itself exports by default the getAction-wrapped variant of each of these actions, while also exporting the internal implementation in case it's useful to make an explicit, direct call.

I'm mocking this up here to see if this approach seems reasonable before doing more because its quite a big refactor.

---

PR-Codex overview

This PR focuses on refactoring functions in various action files to directly call getBlock, getBlockNumber, and getChainId functions instead of using getAction.

Detailed summary

• Replaced getAction calls with direct calls to getBlock, getBlockNumber, and getChainId functions in multiple files.
• Updated function signatures and parameters accordingly.
• Removed unnecessary getAction imports from specific files.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9d97e93

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@holic is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

[holic]

this was already in the union a few lines above

[holic]

we call getBlock here, so this error type should also be included here?

[roninjin10]

My worry here is if this pattern is expected, that means third party actions will also need to remember to implement it.

Maybe this is a unimportant because a third party action is less likely to be overriden.

Maybe a solution to that would be to encourage folks to build actions using a defineAction(...) utility or something?

[roninjin10]

Is it actually necessary to export both? Shouldn't getBlockNumber always "just work"?

[holic]

My understanding is if I override getBlockNumber with my own action, then inside that override call into viem's getBlockNumber here, it'd end up resolving to my own getBlockNumber, not viem's underlying one, because that's the one attached to the client object?

That points to a potentially deeper issue though - would this result in an infinite loop?

[roninjin10]

Suggested change

	>(
	client: Client<Transport, chain, account>,
	params: GetBlockParameters<includeTransactions, blockTag> = {},
	): Promise<GetBlockReturnType<chain, includeTransactions, blockTag>> {
	return getAction(client, _getBlock, 'getBlock')(params)
	}
	>(
	client: Client<Transport, chain, account>,
	params: GetBlockParameters<includeTransactions, blockTag> = {},
	): Promise<GetBlockReturnType<chain, includeTransactions, blockTag>> {
	return getAction(client, _getBlock, 'getBlock')(params)
	}

Might be able to do this just to save some boilerplate

const withGetAction = <TAction>(action: TAction, name: string): TAction => {
  return ((client, params) => {
     return getAction(client, action, name)(params)
  }) as unknown as TAction
}

export const getBlock = withGetAction(_getBlock, 'getBlock')

[roninjin10]

DOn't do this it's convenient but will make stack traces suck

[holic]

means third party actions will also need to remember to implement it

this is already true for getAction today, which isn't correctly used in most cases

[holic]

Another thing I am realizing that I don't think I fully internalized: viem clients only support _one_ instance of a given action, rather than a stack of an action (like middleware).

So if I have two decorators that each override getChainId, only the most recently used one (called via .extend) will be attached to the client and called by all other actions.

Which makes sense, because the action ultimately calls out to another lower level action or RPC method.

I have a use case where I override writeContract to allow submitting txs to the mempool serially to ensure nonce ordering. In this action, I wanted to internally call whatever the underlying writeContract action is on the client, to preserve original behavior. But that would be my own writeContract if you extended the client with this action, rather than the one attached before it?

Nevermind, it does work like a stack of middleware. Test PR coming!