kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Edit GraphQL general availability text

Browse source
This commit is contained in:
Evan Read 2019-07-10 18:11:06 +00:00 committed by Achilleas Pipinellis
parent 8a6a1c8f9f
commit 877395b17b
2 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/api/README.md
View file

@ -154,9 +154,10 @@ the `/Users` endpoint. The base URL is: `/api/scim/v2/groups/:group_path/Users/`
## Road to GraphQL
Going forward, we will start on moving to
[GraphQL](graphql/index.md) and deprecate the use of
controller-specific endpoints. GraphQL has a number of benefits:
[GraphQL](graphql/index.md) is available in GitLab, which will
allow deprecation of controller-specific endpoints.
GraphQL has a number of benefits:
1. We avoid having to maintain two different APIs.
1. Callers of the API can request only what they need.

6
doc/api/graphql/index.md
View file

@ -1,6 +1,8 @@
# GraphQL API
> [Introduced][ce-19008] in GitLab 11.0.
> - [Introduced][ce-19008] in GitLab 11.0 (enabled by feature flag `graphql`).
> - [Always enabled](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30444)
in GitLab 12.1.
[GraphQL](https://graphql.org/) is a query language for APIs that
allows clients to request exactly the data they need, making it
@ -29,8 +31,6 @@ There are no plans to deprecate the REST API. To reduce the technical burden of
supporting two APIs in parallel, they should share implementations as much as
possible.
As of the 12.1 release, GraphQL is always enabled.
## Available queries
A first iteration of a GraphQL API includes the following queries