You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am reading about the github api to work on #7. I realized github has a fantastic graphql api. Did a quick implementation and it allows us to get all the data we need in one go. Here is an example if you want to try out. Use graphql explorer to run this...
Its cool, isn't 😎
I think we can completely skip #7 and #4 and implement them in one go using graphql. I know its a lot of rewrite, but let me know your comments 😄
The text was updated successfully, but these errors were encountered:
This looks very cool indeed: GraphQL wasn't available when I had initially written the bot. :)
I don't see a rewrite being a problem at all. Also, a cursory glance suggests that the GraphQL query would still require making n queries for n labels (i.e. no out-of-box support for logical operators like OR/AND). We will be able to avoid the extra call to get the primary languages though.
Also, with GraphQL, having an OAuth token would be a necessary.
Yes, you are right about n queries. Am trying to figure out if there is a better way of doing it. I posted the question on github forum but haven't got any reply so far. 🙁 Doing n queries with graphql is going to be pain because we need to remove the duplicates from the returned objects because of multiple tags. I am trying my best to avoid it 🙂
True, we can avoid multiple calls for languages and we can directly ask for the primary language 😍
While I wait for the github guys to get back to me, I will try to implement the alternate approach over the weekend and see how it goes.
Hey @musically-ut,
I am reading about the github api to work on #7. I realized github has a fantastic graphql api. Did a quick implementation and it allows us to get all the data we need in one go. Here is an example if you want to try out. Use graphql explorer to run this...
and this in the query variables...
which will return a bunch of these....
Its cool, isn't 😎
I think we can completely skip #7 and #4 and implement them in one go using graphql. I know its a lot of rewrite, but let me know your comments 😄
The text was updated successfully, but these errors were encountered: