You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2024. It is now read-only.
The problem I'm facing in 7.9.0-beta is that operationName property of my query class is always generating with the value that equals the output file name. So, when I'm using unnamed source query, the request fails with an error like "Unknown operation named ...". I tried to turn off the generate_queries option but nothing changed. The only way to solve this is to name raw queries explicitly. Is there any way to turn off the feature that generates operation names? Or is there any other approach you recommend.
Specs
Artemis version: 7.9.0-beta
The text was updated successfully, but these errors were encountered:
Could you attach Any code samples to demo the issue?
The issue template asked you to do that…
fill the issue properly to get help(with schemas and queries for reproduction)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug description
The problem I'm facing in 7.9.0-beta is that operationName property of my query class is always generating with the value that equals the output file name. So, when I'm using unnamed source query, the request fails with an error like "Unknown operation named ...". I tried to turn off the generate_queries option but nothing changed. The only way to solve this is to name raw queries explicitly. Is there any way to turn off the feature that generates operation names? Or is there any other approach you recommend.
Specs
Artemis version: 7.9.0-beta
The text was updated successfully, but these errors were encountered: