Repository navigation
chore: regenerate the models for statement-row units - #232
Merged
Merged
Conversation
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.
Summary
Regenerates the client against the API as of v1.15.13 (robosystems#1690). It picks up one new optional response field and one description update. The local stack it was generated from was current with
origin/main.Changes
Regenerated
models/(generated output, no hand-written changes):AnalyticalStatementFactRow.unit(optional) is added. A financial-statement-analysis row now says its unit (USD,USD/shares). A line a filer reports in two units, its own currency and a US-dollar translation, comes back once per unit.CreateViewRequest.include_summary: description only. An element reported in more than one unit gets no summary.No facade under
robosystems_client/clients/changes. No facade groups, dedups or indexes statement rows, so a line that now appears once per unit passes through unchanged.Compatibility
ADDITIVE, so it rides a client minor. Prod is on v1.15.12 and does not serve
unityet. Until the v1.15.13 deploy the field reads asUNSET, so this is safe to release before the deploy.Release-note line:
AnalyticalStatementFactRow.unit.Testing
just test-all: 617 passed, 17 skipped; ruff, format and basedpyright are clean. The pre-push hook re-ran the same gate.🤖 Generated with Claude Code