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.

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

Expose GitHub GraphQL API? #453

Open
ashfurrow opened this issue Aug 9, 2019 · 2 comments
Open

Expose GitHub GraphQL API? #453

ashfurrow opened this issue Aug 9, 2019 · 2 comments
Labels

Comments

@ashfurrow
Copy link
Member

Hey! So we were building a new feature for Artsy's Peril use and wanted to use GitHub's GraphQL api. danger.github.api returns an octokit/rest.js instance, but I'm wondering if Peril could expose an octokit/graphql.js instance as well? Or is this maybe already exposed, but I can't see it? A workaround exists but getting first-party support would be awesome.

If this seems like a worthwhile feature, I'd be down to work on it 👍

@orta
Copy link
Member

orta commented Aug 9, 2019

This isn't really a peril-level abstraction, it's a danger one - regardless I could see danger supporting that for sure.

Looks like they share their dependencies anyway 👍

@ashfurrow
Copy link
Member Author

Ah right, of course! Okay cool, I'll dig into that tomorrow at Peer Lab 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants