Skip to content

Conversation

egelhaus
Copy link
Collaborator

@egelhaus egelhaus commented Aug 4, 2025

What kind of change does this PR introduce?

eg: Bug fix, feature, docs update, ...

Why was this change needed?

Please link to related issues when possible, and explain WHY you changed things, not WHAT you changed.

Other information:

eg: Did you discuss this change with anybody before working on it (not required, but can be a good idea for bigger changes). Any plans for the future, etc?

Checklist:

Put a "X" in the boxes below to indicate you have followed the checklist;

  • I have read the CONTRIBUTING guide.
  • I checked that there were not similar issues or PRs already open for this.
  • This PR fixes just ONE issue (do not include multiple issues or types of change in the same PR) For example, don't try and fix a UI issue and include new dependencies in the same PR.

Copy link

vercel bot commented Aug 4, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
postiz ⬜️ Ignored (Inspect) Aug 4, 2025 9:46pm

@egelhaus egelhaus requested a review from Copilot August 4, 2025 21:36
Copilot

This comment was marked as outdated.

@egelhaus egelhaus requested a review from Copilot August 4, 2025 21: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 adds automatic error reporting dialog functionality to the Sentry client initialization. The change implements a beforeSend hook that displays Sentry's report dialog whenever an exception occurs, allowing users to provide additional context about errors.

  • Adds a beforeSend hook to show Sentry report dialog on exceptions
  • Includes error handling to prevent the error reporting mechanism from causing additional errors

} catch (err) {
// Prevent error reporting from causing its own errors
// Optionally log the error for debugging
// console.error('Failed to show Sentry report dialog:', err);
Copy link
Preview

Copilot AI Aug 4, 2025

Choose a reason for hiding this comment

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

According to the project's Sentry logging guidelines, error logging should use Sentry's structured logger instead of console.error. Consider using logger.error() from Sentry with appropriate context if this line is uncommented.

Copilot generated this review using guidance from copilot-instructions.md.

@egelhaus egelhaus requested a review from nevo-david August 4, 2025 21:41
@egelhaus egelhaus added the sentry label Aug 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant