fix(sdk): define tracing response types locally instead of importing from Fern client #3442
+25
−1
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
AgentaNodeDtoandAgentaNodesResponselocally in SDKChanges
sdk/agenta/sdk/types.py: Added local definitions for
AgentaNodeDtoandAgentaNodesResponse, replacing the import fromagenta.client.backend.types.Why
These types are SDK-internal models used for inline trace responses. They were previously imported from Fern-generated client types, but:
Defining them locally makes the SDK self-contained and independent of Fern generation quirks.
Type Definitions
Testing
sdk/agenta/sdk/tracing/inline.pyandsdk/agenta/sdk/engines/tracing/inline.pyextra="allow"to accept arbitrary fields when constructed from span dictionaries