Skip to content
Snippets Groups Projects
Commit abeae9f4 authored by Jacob Schatz's avatar Jacob Schatz
Browse files

Remove GraphQL from future plans.

parent b8b49938
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -59,19 +59,6 @@ following locations:
- [V3 to V4](v3_to_v4.md)
- [Version](version.md)
 
## Road to GraphQL
Going forward, we will start on moving to
[GraphQL](http://graphql.org/learn/best-practices/) and deprecate the use of
controller-specific endpoints. GraphQL has a number of benefits:
1. We avoid having to maintain two different APIs.
2. Callers of the API can request only what they need.
3. It is versioned by default.
It will co-exist with the current v4 REST API. If we have a v5 API, this should
be a compatibility layer on top of GraphQL.
## Basic usage
 
API requests should be prefixed with `api` and the API version. The API version
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment