Skip to content

fix: improve api error messages #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 11 commits into
base: main
Choose a base branch
from
Open

Conversation

fmenezes
Copy link
Collaborator

No description provided.

@fmenezes fmenezes marked this pull request as ready for review April 30, 2025 09:38
@Copilot Copilot AI review requested due to automatic review settings April 30, 2025 09:38
@fmenezes fmenezes requested a review from blva as a code owner April 30, 2025 09:38
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR improves the API error messaging in the atlas client by refining the error detail extraction and formatting.

  • Introduces an additional parameter (body) to capture detailed API errors.
  • Refactors the static error construction method to handle both JSON and text responses gracefully.

@fmenezes fmenezes requested a review from a team as a code owner April 30, 2025 09:47
try {
text = await response.text();
} catch {
text = "";
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we set to something like "couldn't fetch error" or "unknown error" too

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

private constructor(
message: string,
public readonly response?: Response,
public readonly body?: ApiError
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a benefit to us storing the body?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Getting the ApiError model gives us insight into backend error codes, some tools might require an if/else depending on the backend error code.

@gagik
Copy link
Collaborator

gagik commented Apr 30, 2025

Looks good but I agree we should hold off from merging/releasing for the time being like with #161 as it's not super critical yet.

@fmenezes
Copy link
Collaborator Author

@gagik I think this change fixes type errors from apiClient

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.

3 participants