-
Notifications
You must be signed in to change notification settings - Fork 36
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
Stop using Severity enum #431
Conversation
Please validate your changes locally and make sure CI passes - see https://github.com/DiederikvandenB/apollo-link-sentry/blob/master/CONTRIBUTING.md |
Hey, just to help move this PR along. Looks the migration guide expects you to use the string value now not the enum. E.G. |
Yeah, that's why I'm using The issue here is we need to bump |
You can make whatever changes are required to make this pull request pass. |
Yeah, that test is failing because of the options type, which is inherited from https://github.com/wix/sentry-testkit and it looks like they didn't add support for Sentry 7 yet. |
Are we stuck waiting for zivl/sentry-testkit#108 or can we work around this issue? |
I think we can wait for zivl/sentry-testkit#109 |
# [3.2.0](v3.1.3...v3.2.0) (2022-07-07) ### Features * use `SeverityLevel` over `Severity` enum ([#431](#431)) ([e758576](e758576))
🎉 This PR is included in version 3.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
getsentry/sentry-javascript#4926