Regenerate for named SQL parameters and operator descriptions - #184
Merged
Merged
Conversation
Picks up three API-side changes: - SqlStatementRequest.parameters now accepts an object as well as a list, for named placeholders ($param_name) alongside positional ones (? / $1). Adds SqlStatementRequestParametersType1. - Operator descriptions name the operators that are actually registered — cypher and mapping — instead of the retired financial / research / rag trio and their fixed per-mode credit prices. - live-financial-statement lists cash_flow_statement among its statement types. Additive to the generated tier: no removals, no stable-tier change.
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.
Routine regeneration against the current
mainAPI surface. Three changes came across, one of them a real type widening rather than prose.What changed
SqlStatementRequest.parametersaccepts an object as well as a list. The API-side field is nowlist[Any] | dict[str, Any] | None, so named placeholders ($param_name) are expressible alongside positional ones (?/$1) — the two forms still cannot be mixed in one statement. Generation addedSqlStatementRequestParametersType1(the object arm) and the union-parsing branches into_dict/from_dict.Operator descriptions now name the operators that exist. They advertised
financial,research, andragwith fixed per-mode credit prices (quick5-10,standard15-25,extended30-75). What is actually registered iscypherandmapping, and credits are consumed by real token usage, not a per-mode price. The new text also points atGET /v1/graphs/{graph_id}/operatoras the live answer, so the docstring cannot drift the same way again.LiveFinancialStatementRequest.statement_typelistscash_flow_statementamong its statement types.Compatibility
Generated tier, additive: a widened request-field union and a new model export. No removals, no stable-tier change — nothing here is in the facades, the root exports, or the emit-path symbols the integration template imports. Rides a minor; no deprecation cycle and no curated release notes required.
Verification
Each of the three source-side changes was confirmed present at
robosystemsorigin/main, not just on a local feature branch, so the regeneration reflects merged API state.just test-allgreen via the pre-commit gate: 526 passed, 17 skipped, ruff clean, 0 basedpyright errors.