diff options
| author | Jacob Schatz <jschatz1@gmail.com> | 2017-09-05 22:35:58 +0300 |
|---|---|---|
| committer | Jacob Schatz <jschatz1@gmail.com> | 2017-09-05 22:35:58 +0300 |
| commit | abeae9f4e61c4c9da8001fa858441cf64ea0e0d5 (patch) | |
| tree | 0bfef2694083c634a09936ca90bd5e38dc1192ce | |
| parent | b8b4993805c620f6c29f3189b6e151c47854c5b7 (diff) | |
Remove GraphQL from future plans.
| -rw-r--r-- | doc/api/README.md | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/doc/api/README.md b/doc/api/README.md index c2a08dcff07..d3b7c9e6ef1 100644 --- a/doc/api/README.md +++ b/doc/api/README.md @@ -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 |