Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Allow others to trace execute_field GQL event #93

Merged
merged 1 commit into from
Apr 2, 2024

Conversation

janko
Copy link
Contributor

@janko janko commented Apr 2, 2024

Follow-up to #91.

The new tracing API works in a way that modules get included into a GraphQL::Tracing::Trace class, which provides a no-op #execute_field implementation that just yields. If we don't call super, other tracing modules that override #execute_field as well, that got included before batch-loader, won't get executed, because yield will short-circuit the execution.

The new tracing API works in a way that modules get included into a
`GraphQL::Tracing::Trace` class, which provides a no-op `#execute_field`
implementation that just yields. If we don't call `super`, other tracing
modules that override `#execute_field` as well, that got included before
batch-loader, won't get executed, because `yield` will short-circuit the
execution.
@exAspArk exAspArk merged commit fc4e0fe into exAspArk:main Apr 2, 2024
@janko janko deleted the graphql-trace-with-super branch April 2, 2024 13:09
@exAspArk
Copy link
Owner

exAspArk commented Apr 2, 2024

Super! 🎉

I just released this fix in v2.0.4. Thank you!

@janko
Copy link
Contributor Author

janko commented Apr 2, 2024

Thanks, I appreciate the quick release ❤️

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants