-
Notifications
You must be signed in to change notification settings - Fork 441
Decouple object safe part from GraphQLType #685
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
Conversation
|
Is the perf noticeable switching from static to dynamic dispatch? |
|
@LegNeato we do not switch from static to dynanic dispatch in this PR. This PR touches nothing perf-related. It just refactors traits definitions in the way making dynamic dispatch possible to use in future. Current |
|
Apologies, hadn't looked at the code yet :-) |
# Conflicts: # juniper/CHANGELOG.md
a6bbe78 to
af26c5e
Compare
Revealed from #682
Required for #682
Overview
Decouples object safe part of
GraphQLTypetrait into a separateGraphQLValuetrait. Does the same forGraphQLTypeAsyncandGraphQLSubscriptionTypetoo.Motivation
This change allows to use dynamic dispatch via resolving
GraphQLValuetrait objects.