-
-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
why not includes the GraphQL? #562
Comments
In which chart? Frontend? Backend? DevOps? |
Frontend |
It should be in backend as well. |
Both side Back and Front and Apollo as favorite tech. After maybe Relay.... others (I don't know others well o_O) |
This has been fixed and will be published in the coming release. Thank you 🙏 |
I daresay that in Backend, GraphQL should be in "Learn about APIs" at this point, given the rate of adoption. REST should definately be learned always as a prerequesite to implementing GraphQL over HTTP, so the "learn at any time" legend key would remain, though GraphQL has a much broader scope and application than HTTP webservice APIs, all of it's applications would fall under the broad category of "APIs". Should I open a new ticket? that said, the place where it sits still makes sense, since it tends to be at the front of a "backend" stack (for example, to stitch service interfaces together into a common schema) |
why not includes the GraphQL?
https://github.com/topics/github-api
https://developer.github.com/
The text was updated successfully, but these errors were encountered: