Skip to content
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

fix(api): error messages #58

Merged
merged 3 commits into from
Aug 5, 2024
Merged

fix(api): error messages #58

merged 3 commits into from
Aug 5, 2024

Conversation

argl
Copy link
Contributor

@argl argl commented Aug 5, 2024

Description

Error message should be generic, this removes host names from the resolver error.

(MP-1397)

Motivation

These get forwarded to telemetry, so these should be only error classes with no individual information conatined.

@argl argl marked this pull request as ready for review August 5, 2024 09:54
@argl argl requested a review from a team as a code owner August 5, 2024 09:54
Copy link
Member

@LeoMcA LeoMcA left a comment

Choose a reason for hiding this comment

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

Code looks fine, I'll point out one thing: I think the error message we show in UI also comes from this error message, the value of having the host in the message is the user sees what the specific host observatory can't resolve is (which is important, because it gets processed a bit, e.g. an input of https://example.com/foobar turns into example.com). Perhaps the error should just be genericised on the frontend, before being sent to glean, or the host should be sent as a separate field in the error response. Or you decide this isn't a problem - also acceptable, just wanted to point it out

@argl argl changed the title Mp 1397 generic error messages fix(api): error messages Aug 5, 2024
@argl argl merged commit efe3ea3 into main Aug 5, 2024
4 checks passed
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.

2 participants