-
Notifications
You must be signed in to change notification settings - Fork 52
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
port to graphql!?! #139
Comments
And finally real, GitHub-provided types! I'm investigating this now (but it will likely be some time before it leaves Early Access). In the mean time, we'll have 1.2 and maybe 1.3 but we should start building the infrastructure for 2.0. |
I'm crying tears of typing joy |
The GraphQL API is out of Early Access: https://github.com/blog/2359-introducing-github-marketplace-and-more-tools-to-customize-your-workflow |
GraphQL server in OCaml: https://discuss.ocaml.org/t/ann-graphql-0-1-0/282 |
I have something working now, which may be of interest: andreas/ocaml-graphql-server#56 I would be happy to hear if you have any thoughts on how |
Here's a simple example of how it could work with If you check out the branch locally, you can build with |
@andreas did you delete the github example? |
It's available here: https://github.com/andreas/ppx_graphql/blob/master/examples/github.ml |
A lot has changed since and the v3 API is getting slowly deprecated, the transition is imminent, see more at:
It will require GraphQL library by @andreas. See its repository at andreas/ocaml-graphql-server. |
Actually the GraphQL PPX I mentioned above is no longer available in The most mature GraphQL PPX library is currently |
@XVilka Contrary to what you are claiming the GitHub REST API (v3) is not at all getting deprecated. In issue ocaml-opam/opam-publish#97, the title is misleading, it's just the authentication method that is getting deprecated. There isn't much point in porting the The |
The fix for that opam-publish issue was made in this PR, available in 4.3.0. |
@roddyyaga it broke the authorization though, see:
Thus, current recommendation is to use 4.2.0 instead. |
http://githubengineering.com/the-github-graphql-api/ -- fewer data transferred than using the REST API
The text was updated successfully, but these errors were encountered: