BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
abeae9f4
Commit
abeae9f4
authored
Sep 05, 2017
by
Jacob Schatz
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove GraphQL from future plans.
parent
b8b49938
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
13 deletions
+0
-13
README.md
doc/api/README.md
+0
-13
No files found.
doc/api/README.md
View file @
abeae9f4
...
...
@@ -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