Skip to content

feat(errors): preserve response error metadata - #402

Draft
kartojal wants to merge 1 commit into
mainfrom
feat/dev-670-error-metadata
Draft

kartojal wants to merge 1 commit into
mainfrom
feat/dev-670-error-metadata

Conversation

@kartojal

@kartojal kartojal commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Response errors now expose optional retryable, trace_id, and parameter fields. A valid body trace ID takes precedence over x-trace-id; absent or malformed metadata stays None. Sync and async transports retain the existing error classes, messages, status/code handling, trading restrictions, heartbeat recovery, and retry behavior.

Contract verified against the public Data API OpenAPI and a live, unauthenticated validation response. Covers DEV-670.

Validation: 3,592 non-integration tests passed, including 117 focused transport/metadata/retry cases; Ruff lint and format, Pyright, package build, and git diff --check passed. Read-only Review SDK PR completed; added missing-metadata coverage identified during review, with no remaining actionable findings.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant