-
Notifications
You must be signed in to change notification settings - Fork 101
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
Inline fragments not working with use_struct_references: true
and pointer: optional
#278
Comments
Is it possible to just apply the |
Apologies for the delay in responding, this issue got buried. This may be useful input to how we tune these options ( |
Oh interesting, I didn't know that was possible. Thanks for the info! |
I'll leave up to you to close if you desire :) @benjaminjkraft |
Describe the bug
Seems like turning on
use_struct_references
and settingpointer: optional
breaks the ability to read from inline fragments.To Reproduce
Problem happens at runtime.
Setting
use_struct_references: true
andpointer: optional
leads to the removal of the interface(?) that is supposed to be usable for grabbing data from inline fragments.In the docs design.md, there is a block of code similar to
While this code doesn't throw a compiler error with the default config, when you adjust the config vars mentioned above, doesn't seem like there is a way to get the inline fragment data. Messages similar to
invalid operation: transaction.PaymentMethod.GetDetails() (value of type *destination.ChargeCreditCardChargeCreditCardTransactionPayloadTransactionPaymentMethodDetails) is not an interface
pop up.I am using this library to query/send mutations to Braintree. The reason I set the config vars above is primarily because Braintree's API doesn't handle Golang default values for Braintree's GraphQL inputs.
Here's what this mutation looks like:
Expected behavior
Generating code in such a way that this behavior works. Unless I'm doing something incorrectly/sub-optimally?
genqlient version
main
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: