Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
heptapod
heptapod
Commits
fbbe1345aafe
Commit
abeae9f4
authored
Sep 05, 2017
by
Jacob Schatz
Browse files
Remove GraphQL from future plans.
parent
13fa37dc5690
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/api/README.md
View file @
fbbe1345
...
...
@@ -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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment