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

[CORL-1293] Sentry Error Integration #3109

Merged
merged 9 commits into from Aug 20, 2020
Merged

[CORL-1293] Sentry Error Integration #3109

merged 9 commits into from Aug 20, 2020

Conversation

wyattjoh
Copy link
Collaborator

What does this PR do?

  • Adds support for Sentry error reporting to the core.
  • Replace custom GraphQL wrappers around apollo-server-express with vanilla implementation.

What changes to the GraphQL/Database Schema does this PR introduce?

None.

How do I test this PR?

TBD

@kgardnr kgardnr modified the milestones: v6.3.3, v6.4.0 Aug 15, 2020
@wyattjoh wyattjoh marked this pull request as ready for review August 19, 2020 20:10
// Parse the config from the element text, it should always be a valid JSON
// string if the element is available. We should allow the error to bubble if
// we are unable to parse it.
const config: StaticConfig = JSON.parse(element.innerText);
Copy link
Contributor

Choose a reason for hiding this comment

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

this is a bit scary, is there a reason we can't pass these values around like other config values?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We want the error reporter setup as early as possible. Otherwise we won't capture network related errors. This is the same mechanism that we pass updates to the public path (See src/core/build/publicPath.js).

return {
id: user.id,
username: user.username || undefined,
email: user.email || undefined,
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need to send email to the error reporter? I'd feel more comfortable if it was just id

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The email was to aid in responding to users that experience errors, but we can certainly remove it!

@kgardnr kgardnr modified the milestones: v6.4.0, v6.3.3 Aug 20, 2020
@kgardnr kgardnr added the 🚀 merge it! Pull requests that should be merged after status checks pass with a review label Aug 20, 2020
@kodiakhq kodiakhq bot merged commit 15f7c10 into master Aug 20, 2020
@kodiakhq kodiakhq bot deleted the feature/CORL-1293 branch August 20, 2020 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 merge it! Pull requests that should be merged after status checks pass with a review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants