feat: typed PrimeApiError handling (v1.12.0) - #5
Merged
Conversation
✅ Heimdall Review Status
|
rcbgr
requested changes
Sep 1, 2026
…rror. Keep the old names as aliases so existing except clauses continue to work. Co-authored-by: Cursor <cursoragent@cursor.com>
cfluke-cb
changed the title
cfluke-cb
force-pushed
the
carl-fluke/update-spec-2026-08-28-futures
branch
from
September 1, 2026 14:36
a55a763 to
42f9974
Compare
rcbgr
approved these changes
Sep 3, 2026
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
3 participants
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.
Description
Raise typed Prime API errors from
Client.requestand move generated*ErrorResponsemodels intoprime_sdk/generated/errors.py. JSON error bodies now populatecode,subcode,trace_id, and a generatedbodydataclass on HTTP-status subclasses ofPrimeApiError.Canonical exception names are
PrimeSdkErrorandPrimeApiError. The previousPrimeSDKErrorandPrimeAPIErrornames remain as aliases.Rebased onto
mainafter v1.11.0 landed in #4.Type of Change
Checklist