chore(sdk): regenerate for the analyst operator rename - #198
Merged
Conversation
Docstrings only: the operator endpoints now describe `analyst` (formerly `cypher`, which the API still accepts as an alias) — see robosystems #1308. No request or response shape changed.
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
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
Regeneration for the operator rename in robosystems #1308: the read-only question-answering operator is now registered as
analyst(cypher, its former name, stays accepted by the API as an alias). The only thing that reaches this package is descriptive text — the operator endpoints' docstrings.Changes
robosystems_client/api/operator/—auto_select_operator.py,execute_specific_operator.py,get_operator_metadata.py. Net effect on the public surface: none. The endpoint docstrings now describeanalyst(curated financial reads, documents, memory, read-only Cypher as the fallback) and notecypheris accepted as its former name; theoperator_typepath parameter's example reads'analyst', 'mapping'. Sync and async variants of each endpoint carry the same text. No model, signature, or field changed.robosystems_client/clients/operator_client.py) untouched — the facade passesoperator_typethrough and never hardcoded the name.Compatibility
INTERNAL — docstring text in generated modules; no emitted model, export, or signature changed. Runtime note for consumers, not a package change: once the API release ships, responses report
operator_used: "Analyst Operator"andGET /v1/graphs/{g}/operatorlistsanalystinstead ofcypher;operator_type="cypher"keeps working.Testing
just test-allvia the pre-commit hook: pytest 526 passed / 17 skipped, ruff check clean, ruff format clean, basedpyright 0 errors.mainat #1308 (just generate-sdk); GraphQL schema unchanged, so the codegen drift gate is unaffected.