mirror of
https://github.com/atulmy/gql-query-builder.git
synced 2026-04-25 23:55:55 +03:00
[GH-ISSUE #72] Allow naming mutations #140
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gql-query-builder#140
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @seantalbot-jisc on GitHub (Jul 27, 2022).
Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/72
The
gql.queryfunction takes an optional config object in which I can pass anoperationNameto 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 theoperationNamehttps://mswjs.io/docs/getting-started/mocks/graphql-api#request-handlerThe
gql.mutationfunction 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?
@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.
@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