Repository navigation
Conversation
This branch has not been deployed
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
The Python SDK linked 401 errors to the TypeScript setup guide, and 405 errors fell back to a generic unexpected-error message. Point 401 diagnostics to the current credential setup guide and name the settings to verify. Give 405 errors a distinct message with base URL and server compatibility checks, and keep the support link.
Verification


Confidence Score: 5/5
This PR appears safe to merge.Summary
This PR makes 401 and 405 error messages more useful without changing how requests or exceptions work.
No actionable issues found.
Reviews (1) · Last reviewed commit: "fix(sdk): make 401 and 405 API diagnosti..." · Reviewed by Greptile