Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
See #45 that fixes the related test. Not sure how this slipped in.
Closing via #45
> It looks like this may be caused by things down in `graphql` itself, in which case we're pinning `graphlient` versions until I can convince the API team to do...
Not sure, but this might be helpful: https://github.com/rmosolgo/graphql-ruby/pull/2327 and https://github.com/github/graphql-client/issues/211 (another client) If you find out how to do this, let's document it!
Bump @manekinekko.
Unfortunately this is now hitting https://github.com/actions-on-google/actions-on-google-nodejs/issues/16. And they [don't seem to want tests](https://github.com/actions-on-google/actions-on-google-nodejs/pull/12) :(
For now just wait till https://github.com/actions-on-google/actions-on-google-nodejs/pull/17 is merged and 1.0.8 is released.
Maybe @manekinekko you can ping someone at Google about this, like @smishra2?
Yes, because if you decide to give up @suweller there's no way anyone can reclaim this repo and its administration. Just trying to help reduce potential bus factor.
I am around if I can be of any help!