Skip to content
Snippets Groups Projects
Commit 877395b1 authored by Evan Read's avatar Evan Read Committed by Achilleas Pipinellis
Browse files

Edit GraphQL general availability text

parent 8a6a1c8f
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -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.
Loading
Loading
# 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
Loading
Loading
@@ -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
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