docs(examples): add complex-type parameters example#338
Merged
Conversation
No example exercised custom types as transaction parameters, so the TII `components.schemas` emission had no end-to-end coverage in examples/. Add complex_type_params.tx3 covering the full surface in one buildable file: a record param, a nested record (recursive `$ref`), a `oneOf` variant param, a transparent type alias, and a `List<Record>` param. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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
Add
examples/complex_type_params.tx3— a single buildable example thatexercises custom types as transaction parameters, which is what drives the
TII
components.schemasemission added in #337.Why
No example in
examples/used a record/variant type as atxparameter orenvfield, so the new schema emission had zero end-to-end coverage there(only
tii::schemaunit tests). The two existing files that take custom-typeparams (
jpg.tx3,levvy.simple.tx3) don't currently parse.Coverage in one file
Order→ object schema, referenced by$refOrder.asset: AssetClass→ recursive$ref, registered onceSide→ taggedoneOfLovelace = Int→ inlined transparently (no schema of its own)List<Record>—place_many(orders: List<Order>)→ array whoseitemsis a$refVerified:
tx3c build … --emit tiiyieldscomponents.schemas = { AssetClass, Order, Side }with the expected$refs andoneOf.🤖 Generated with Claude Code