Support child array paths in interpolated intents - #54
Merged
manuelwedler merged 7 commits intoJul 29, 2026
Merged
Conversation
manuelwedler
approved these changes
Jul 29, 2026
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.
Summary
items.[].amountitems.[]interpolatedIntentplaceholders with item-scoped token formattingThe interpolation code can stay unchanged because it already resolves placeholders from the
renderedValuesmap.Context
This was surfaced while testing the Ocarina ERC-7730 registry submission: ethereum/clear-signing-erc7730-registry#2598.
That descriptor uses an EIP-712
interpolatedIntentlike:The referenced field is formatted as
tokenAmountusing an item-scopedtokenPathsuch astips.[].token.Details
This updates array-path metadata tracking so rendered values are joined and stored under the full wildcard path:
items.[]items.[].amounttips.[].amountTop-level array fields still also store the joined value under the base path for compatibility.
Validation
npm testnpm run check:typesnpm run check:prettiernpm run check:eslint