Dmitri Shuralyov

> However when ran from graphql playground using the same authentication token it works. That is unexpected. > Is there a way I can inspect the generated graphql? Yeah, it's...

> I can also confirm I'm getting the data back as expected. So it seems to be something in the lib that is doing some check or magic somewhere after...

> strange thing is we do receive those collaborators regardless in our response. Maybe the results are incomplete? If you think it's a bug on GitHub's side, it would be...

This is a valid use case that `githubql` should support, but currently doesn't (at least I can't think of a way). Thanks for reporting. I'll need to think about how...

One idea I have (that I want to jot down) about how to potentially tackle this is to support `map` types for dynamic queries such as this one. So, your...

Another solution might be to add a new different method that lets you pass a GraphQL query as a string (which you still have to construct yourself), and returns results...

I wanted to post an update here. I also ran into this need recently at: https://github.com/shurcooL/notifications/blob/b2920e64fbc3c388d5191433dd5493c75f302c14/githubapi/githubapi.go#L92-L96 I will continue to think about the best possible resolution to this, and post...

There's been yet another place I would've found this handy: ```Go // fetchCommit fetches the specified commit. func (s *service) fetchCommit(ctx context.Context, repoID int64, sha string) (*commit, error) { //...

@osela There's no progress on this issue from me, because I haven't had any free time left over to think about this. If you're looking to solve this, I'd recommend...

I've made significant progress on this issue this weekend. It turns out it has been _possible_ to perform query batching and/or dynamic queries all along, without any API changes to...