Skip to content
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

__typename support in krystal execution startegy #322

Open
shivangipandey opened this issue Jan 23, 2025 · 0 comments
Open

__typename support in krystal execution startegy #322

shivangipandey opened this issue Jan 23, 2025 · 0 comments
Milestone

Comments

@shivangipandey
Copy link

shivangipandey commented Jan 23, 2025

w.r.t this, in our VajramExecutionStrategy :

QueryAnalyseUtil -> getNodeExecutionConfigBasedOnQuery()

We are passing disableDependentChains from above method, and here it's fetching __typename as well, which will explicitly not be part of the schema, hence it's throwing NPE.

But in general we should have built-in handling for graphQL metadata fields.

And then this field actually is part of response also, and gives TypeName as String. So, we will also have to handle that.

@RamAnvesh RamAnvesh added this to the v9 milestone Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants