GraphQL Interface without fields leads to error in mutation #24803

lfr-ableton · 2019-11-20T16:54:51Z

lfr-ableton
Nov 20, 2019

Hi,

when using the mutation addLabelsToLabelable it returns two fields

clientMutationId (that one is always null in my case)
labelable

I would like to use labelable since I label a PullRequest, which implement the Labelable interface. But that interface has no fields. So I cannot give any field in the mutation, which leads to the error:

Field must have selections (field 'labelable' returns Labelable but has no selections. Did you mean 'labelable { ... }'?)

So the only “workaround” is to use clientMutationId instead and receive the null. But I would like to receive e.g. the title of the labeled Pull Request. Is that possible?

Thanks and Cheers,

Lars

Answered by lee-dohm

Jan 3, 2020

From what I understand, you should be able to use the same ... on PullRequest syntax that you would use in a query that returns multiple object types. So something like this:

mutation {
  addLabelsToLabelable(input: {clientMutationId: "foo", labelableId: "foo", labelIds: [1]}) {
    labelable {
      ... on PullRequest {
        title
      }
    }
  }
}

Let us know if you have more questions.

View full answer

lee-dohm · 2020-01-03T20:01:59Z

lee-dohm
Jan 3, 2020

From what I understand, you should be able to use the same ... on PullRequest syntax that you would use in a query that returns multiple object types. So something like this:

mutation {
  addLabelsToLabelable(input: {clientMutationId: "foo", labelableId: "foo", labelIds: [1]}) {
    labelable {
      ... on PullRequest {
        title
      }
    }
  }
}

Let us know if you have more questions.

0 replies

lfr-ableton · 2020-01-06T14:25:51Z

lfr-ableton
Jan 6, 2020
Author

Thanks a lot,

that does the job!

Cheers,

Lars

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

GraphQL Interface without fields leads to error in mutation #24803

{{title}}

Replies: 2 comments

{{title}}

{{title}}

Select a reply

GitHub Community

GraphQL Interface without fields leads to error in mutation #24803

lfr-ableton Nov 20, 2019

Replies: 2 comments

lee-dohm Jan 3, 2020

lfr-ableton Jan 6, 2020 Author

lfr-ableton
Nov 20, 2019

lee-dohm
Jan 3, 2020

lfr-ableton
Jan 6, 2020
Author