Skip to content

fix(wizard): Ensure API errors are correctly displayed #93788

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

Merged
merged 2 commits into from
Jun 18, 2025

Conversation

mydea
Copy link
Member

@mydea mydea commented Jun 18, 2025

I noticed that the error messages are not displayed at all right now, I guess because the Indicators have been missing. So I added this, and while at it also added some more specific error message for the case when no active DSN can be found in the project.

The DSN error is based on changed here: #93787 but this PR should work unrelated to that still (it will just never show this message).

@mydea mydea self-assigned this Jun 18, 2025
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 18, 2025
mydea added 2 commits June 18, 2025 09:40
I noticed that the error messages are not displayed at all right now, I guess because the `Indicators` have been missing. So I added this, and while at it also added some more specific error message for the case when no active DSN can be found in the project.
@mydea mydea force-pushed the fn/better-wizard-ui-error-handling branch from 6e11faf to e717b80 Compare June 18, 2025 07:43
@mydea mydea merged commit bc8e235 into master Jun 18, 2025
46 checks passed
@mydea mydea deleted the fn/better-wizard-ui-error-handling branch June 18, 2025 07:55
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
I noticed that the error messages are not displayed at all right now, I
guess because the `Indicators` have been missing. So I added this, and
while at it also added some more specific error message for the case
when no active DSN can be found in the project.

The DSN error is based on changed here:
#93787 but this PR should work
unrelated to that still (it will just never show this message).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants