chore(sdk): regenerate against the current API - #204
Merged
Conversation
Picks up `AvailableExtension.display_name`, added in robosystems#1321 —
the endpoint had been computing a display name ("RoboLedger - Accounting
& Financial Reporting") and dropping it when building the response, so
consumers had only the schema slug to render.
Also refreshes two event-block description strings that moved on the API
since the last regeneration. Docstring text only: `transition_to` keeps
the same set of values, so nothing changes shape.
The new field is optional (UNSET default), so nothing breaks against an
API that predates it. The GraphQL SDL snapshot is already current.
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.
Regenerated against a local API running current
main.What moved
AvailableExtension.display_name— the field added in robosystems#1321.The extensions endpoint had been computing a display name ("RoboLedger -
Accounting & Financial Reporting") and then dropping it when building the
response, leaving consumers only the schema slug. Optional (
UNSETdefault),so nothing breaks against an API that predates it.
Two event-block description strings that moved on the API since the last
regeneration (
EventBlockEnvelope.status,UpdateEventBlockRequest.transition_to).Docstring text only — the value sets are unchanged.
The checked-in GraphQL SDL snapshot was already current, so
refresh-schemawas a no-op.
just test-allgreen: 583 passed, 17 skipped; ruff and basedpyright clean.