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.

Sign up for GitHub

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

Jump to bottom

Client.execute should take optional operation_name #21

Closed
barbieri opened this issue Nov 3, 2017 · 2 comments
Closed

Client.execute should take optional operation_name #21

barbieri opened this issue Nov 3, 2017 · 2 comments
Labels
type: feature A new feature
Milestone
Version 3.0

Comments

@barbieri
Copy link

barbieri commented Nov 3, 2017

Eventually the document may contain more than one query or mutation. In this case the queries must be named and operationName should say which one to execute.

Not that useful in real practice, but sometimes while developing it's handy to keep feeding the same file and just change which operation to use.
@barbieri
Copy link
Author

barbieri commented Nov 3, 2017

just saw #17 adds that, close this issue when that's landed.

@Cito Cito added this to the Version 3 milestone May 15, 2020
@Cito Cito added the type: feature A new feature label May 15, 2020
Cito added a commit that referenced this issue May 16, 2020
@Cito
Support different operation names (#21)
3c0bb27
Cito added a commit that referenced this issue May 16, 2020
@Cito
Support different operation names (#21)
0eb4325
@Cito
Copy link
Member

Cito commented May 16, 2020

This feature has now been added in the v2 and v3 (master) branches, so we can finally close this.

@Cito Cito closed this as completed May 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: feature A new feature
Projects
None yet
Milestone
Version 3.0
Development

No branches or pull requests
2 participants
@barbieri @Cito