Skip to content

feat(generator): derive operation bindings - #8

Closed
nmorgan-cb wants to merge 1 commit into
toshi/plan-service-generator-upgradefrom
toshi/generator-operation-bindings
Closed

feat(generator): derive operation bindings#8
nmorgan-cb wants to merge 1 commit into
toshi/plan-service-generator-upgradefrom
toshi/generator-operation-bindings

Conversation

@nmorgan-cb

Copy link
Copy Markdown
Contributor

Description

Stacks on #7 and delivers the compatibility-aware operation binding phase for the full SDK generator.

  • Adds immutable OperationBinding metadata for one OpenAPI operation's Java SDK ownership and names.
  • Adds deterministic binding derivation from the parsed committed spec: tag-based service folders, service names, operation method names, request omission, and pagination.
  • Adds Java compatibility renames for existing public SDK vocabulary and routes the Travel Rule tag into transactions.
  • Adds validation for one-to-one operation coverage, sorted bindings, duplicate Java service methods, and path-parameter declarations.
  • Adds a regression test covering the 103-operation inventory plus representative Orders and Travel Rule binding behavior.

No service source files are generated or replaced in this phase. It establishes the validated contract that the request/response/service emitters will consume in the next stacked PR.

Generated with Toshi

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Dependency update
  • Refactor / cleanup
  • Other (describe below)

Checklist

  • Tests included / updated
  • Changelog updated
  • Version bump if needed

@nmorgan-cb

Copy link
Copy Markdown
Contributor Author

Superseded by #7; its commits were consolidated into the parent draft PR.

@nmorgan-cb nmorgan-cb closed this Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant