Repository navigation
docs(builder-codes): pass dataSuffix per call in Wagmi, add volume - #2091
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Collaborator
✅ Heimdall Review Status
|
soheimam
approved these changes
Oct 9, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed? Why?
dataSuffixon eachsendTransactionandwriteContractcall and in thedataSuffixcapability forsendCalls. AdataSuffixset increateConfigis not applied to transactions sent through a connected wallet (dataSuffixpassed tocreateConfigis not applied to transactions sent through the connector client wevm/wagmi#5248), so the previous config-level setup sent transactions without the Builder Code. The old "Legacy: Per-Transaction Approach" accordion is folded into the main Wagmi steps.dataSuffixcoverssendTransactionandwriteContract, and is forwarded to the wallet as a capability forsendCalls.Transferlogs for attributed transactions. The overview links to it.Notes to reviewers
The Wagmi behavior was reproduced with
@wagmi/core3.6.5 and viem 2.57.4 using an injected connector. Config-leveldataSuffixproduced no suffix onsendTransaction,writeContractorsendCalls. Per-calldataSuffixand thesendCallscapability both produced it.How has it been tested?
node scripts/lint-mdx.json both changed files;node scripts/validate-docs-structure.js;npm test. Type-checked the new volume snippet withtsc --strictand ran its logic against a Base mainnet USDC transfer. Checked the wagmi issue link.Screenshots
Not captured. Affected pages:
/specifications/builder-codes/for-app-developers,/specifications/builder-codes/overview.Generated with Toshi