starred/gql-query-builder
1
0
Fork 0
mirror of https://github.com/atulmy/gql-query-builder.git synced 2026-04-25 23:55:55 +03:00
Code Issues 36 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #72] Allow naming mutations #44

New issue
Closed
opened 2026-03-03 00:02:56 +03:00 by kerem · 2 comments
kerem commented 2026-03-03 00:02:56 +03:00
Owner
Copy link

Originally created by @seantalbot-jisc on GitHub (Jul 27, 2022).
Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/72

The gql.query function takes an optional config object in which I can pass an operationName to name my query. This makes testing queries against a mock GQL server using MSW very easy as I can configure it to respond to incoming queries by the operationName https://mswjs.io/docs/getting-started/mocks/graphql-api#request-handler

The gql.mutation function doesn't take this config object so I can't easily name mutations. This makes testing them with MSW much harder as I have to separately parse the GQL into an AST and locate the name of the underlying mutation that is called.

Could you add this config object to gql-query-builder?

Originally created by @seantalbot-jisc on GitHub (Jul 27, 2022). Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/72 The `gql.query` function takes an optional config object in which I can pass an `operationName` to name my query. This makes testing queries against a mock GQL server using MSW very easy as I can configure it to respond to incoming queries by the `operationName` https://mswjs.io/docs/getting-started/mocks/graphql-api#request-handler The `gql.mutation` function doesn't take this config object so I can't easily name mutations. This makes testing them with MSW much harder as I have to separately parse the GQL into an AST and locate the name of the underlying mutation that is called. Could you add this config object to gql-query-builder?
kerem 2026-03-03 00:02:56 +03:00
kerem commented 2026-03-03 00:02:57 +03:00
Author
Owner
Copy link

@themagickoala commented on GitHub (Nov 30, 2022):

@atulmy I've submitted a PR for this issue. We are hoping to use this package but the operationName for mutations is a hard requirement as we're using MSW too.

<!-- gh-comment-id:1331878609 --> @themagickoala commented on GitHub (Nov 30, 2022): @atulmy I've submitted a PR for this issue. We are hoping to use this package but the operationName for mutations is a hard requirement as we're using MSW too.
kerem commented 2026-03-03 00:02:57 +03:00
Author
Owner
Copy link

@atulmy commented on GitHub (Nov 30, 2022):

@themagickoala thanks for your contribution, the package has been published:
https://www.npmjs.com/package/gql-query-builder/v/3.8.0

<!-- gh-comment-id:1331901523 --> @atulmy commented on GitHub (Nov 30, 2022): @themagickoala thanks for your contribution, the package has been published: https://www.npmjs.com/package/gql-query-builder/v/3.8.0
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
3.8.0
3.7.2
3.7.1
3.7.0
3.6.0
3.5.9
3.5.7
3.5.5
3.5.4
3.5.1
3.5.0
v3.4.1
v3.4.0
3.3.0
3.2.0
3.1.1
3.1.0
3.0.7
3.0.2
2.0.2
Labels
Clear labels   
bug

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
question
No labels
bug
enhancement
enhancement
good first issue
help wanted
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/gql-query-builder#44
No description provided.