Skip to content

Amplify GitLab's GraphQL first policy

Avielle Wolfe requested to merge amplify-graphql-usage-policy into master

What does this MR do and why?

The GitLab engineering docs already specify a preference for GraphQL: https://about.gitlab.com/handbook/engineering/#rails-by-default-vuejs-where-it-counts

And the GitLab API docs already mention that GitLab plans to stop maintaining REST endpoints once the GraphQL API is fully implemented: https://docs.gitlab.com/ee/api/#graphql-api

However, discussions with team members has surfaced that these plans and policies are not widely known. This MR adds additional notes and warnings to make GitLab developers and users aware that they should default to using GraphQL.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports