When the API server returns an unexpected status code, the client currently throws a generic exception without useful context.
It would be helpful to include the HTTP status code, response body, and request URL in the exception message. Better documentation for common error scenarios would also improve the developer experience.
This is a test issue created to verify assigning multiple labels to a single issue.
When the API server returns an unexpected status code, the client currently throws a generic exception without useful context.
It would be helpful to include the HTTP status code, response body, and request URL in the exception message. Better documentation for common error scenarios would also improve the developer experience.
This is a test issue created to verify assigning multiple labels to a single issue.