[GH-ISSUE #19] Operation name #12

New issue

Closed

opened 2026-03-03 00:02:43 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 00:02:43 +03:00

Owner

Originally created by @atulmy on GitHub (Aug 6, 2019).
Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/19

Reference: https://graphql.org/learn/queries/#operation-name

Current:

query {
  thoughts {
    id,
    name,
    thought
  }
}

Option to pass query name ThoughtList

query ThoughtList {
  thoughts {
    id,
    name,
    thought
  }
}

Originally created by @atulmy on GitHub (Aug 6, 2019). Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/19 Reference: https://graphql.org/learn/queries/#operation-name Current: ``` query { thoughts { id, name, thought } } ``` Option to pass query name `ThoughtList` ``` query ThoughtList { thoughts { id, name, thought } } ```

kerem

2026-03-03 00:02:43 +03:00

closed this issue
added the
enhancement

help wanted
labels

kerem commented

2026-03-03 00:02:44 +03:00

Author

Owner

@Devorein commented on GitHub (Jun 29, 2020):

That could be solved by replacing the resultant query via generated.query = generated.query.replace('query',"query "+opName);

But I assume that it could be added to the api itself as part of an argument to the query, mutation and subscription functions.

@Devorein commented on GitHub (Jun 29, 2020): That could be solved by replacing the resultant query via `generated.query = generated.query.replace('query',"query "+opName);` But I assume that it could be added to the api itself as part of an argument to the query, mutation and subscription functions.

kerem referenced this issue

2026-03-15 11:29:00 +03:00

[GH-ISSUE #12] support for primitive return types? #100