We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We can attempt to migrate to a newer API after the following issue in github-graphql is implemented:
github-graphql
hit-on
Since we will write a lot of custom queries for GitHub, I propose the following new module structure:
Hit.Issue
Hit.GitHub.Issue + Hit.GitHub.PullRequest + Hit.GitHub.Milestone + Hit.GitHub.Fork
FromJSON
Once the migration is done, we need to test that our code still works as expected. User-stories to test (feel free to add more):
The text was updated successfully, but these errors were encountered:
[#214] [#214] Initial rewrite to GraphQL
fe6de4c
Resolves #214
[#214] Initial rewrite to GraphQL
535f48b
[#214] New Issue and Milestone additions
56b0999
328047a
chshersh
vrom911
No branches or pull requests
We can attempt to migrate to a newer API after the following issue in
github-graphql
is implemented:hit-on
github-graphql#25Since we will write a lot of custom queries for GitHub, I propose the following new module structure:
Hit.Issue
withHit.GitHub.Issue + Hit.GitHub.PullRequest + Hit.GitHub.Milestone + Hit.GitHub.Fork
FromJSON
instances and functions to fetch relevant informationOnce the migration is done, we need to test that our code still works as expected. User-stories to test (feel free to add more):
The text was updated successfully, but these errors were encountered: