-
Notifications
You must be signed in to change notification settings - Fork 516
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
feat(graphene): Add span for grapqhl operation #2788
feat(graphene): Add span for grapqhl operation #2788
Conversation
This commit adds a span for a graphql operation to the graphene integration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the contribution, and thanks for your patience as we work through our backlog of community PRs!
I noticed that your PR is still using our old, deprecated Hub
APIs. We are going to need to replace these with the new corresponding Scope
APIs before we can merge this PR. More information on how to do this is available in our Migration Guide.
Is this a change you are comfortable with making yourself, or do you need us to take over the PR?
I take the freedom to remove the hubs from the pr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think is is looking good now!
Mostly looks good, see above |
Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com>
Committed your suggestions! Thanks a lot for the quick review! |
This commit adds a span for a GraphQL operation to the graphene integration. Fixes getsentry#2765 --------- Co-authored-by: Anton Pirker <anton@ignaz.at> Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com>
This commit adds a span for a graphql operation to the graphene integration
Fixes #2765
General Notes
Thank you for contributing to
sentry-python
!Please add tests to validate your changes, and lint your code using
tox -e linters
.Running the test suite on your PR might require maintainer approval. Some tests (AWS Lambda) additionally require a maintainer to add a special label to run and will fail if the label is not present.
For maintainers
Sensitive test suites require maintainer review to ensure that tests do not compromise our secrets. This review must be repeated after any code revisions.
Before running sensitive test suites, please carefully check the PR. Then, apply the
Trigger: tests using secrets
label. The label will be removed after any code changes to enforce our policy requiring maintainers to review all code revisions before running sensitive tests.