Add APIError class with HTTP error parsing#13
Merged
Conversation
hectorcast-db
approved these changes
Feb 27, 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
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.
🥞 Stacked PR
Use this link to review incremental changes.
What changes are proposed in this pull request?
Add the core APIError class and fromHttpError factory function, ported from the Go SDK's apierr/apierr.go. This is the main error type that will be returned by all Databricks API calls.
APIError— a transport-agnostic error class extendingErrorwithcode,message,details, and HTTP metadata (status code, headers, body).fromHttpError(statusCode, header, body)— parses HTTP error responses intoAPIError, handling standard, legacy (API 1.2), and SCIM error formats. Returnsundefinedfor 2xx status codes.toCode(httpCode)— maps HTTP status codes to canonicalCodevalues (e.g. 404 →NOT_FOUND, 429 →RESOURCE_EXHAUSTED).error_codeas string or integer, multiple message fields (message,error,detail,scimType), and structured error details.How is this tested?
Unit tests.