Particular connections may have different max page size limits that are higher or lower. Limit Default Max page size 100 records (nodes) per page. The following limits apply to the GitLab GraphQL API. Information about multiplexed queries is also available for GitLab supports batching queries into a single request More ![]() See the GraphQL API Reference for up-to-date information.Īpp/graphql/types/query_type.rb. New associations and root level objects are regularly added. snippets Snippets visible to the signed-in user. metaData Metadata about GitLab and the GraphQL API. users Information about a collection of users. currentUser Information about the signed-in user. namespace The namespace and the projects in it. user Information about a particular user. The GraphQL API includes the following queries at the root level: Query Description project Project information and many of its associations, such as issues and merge requests. View the list of items removed in previous releases. 13.6 The removal in 14.0 allows for 6 months of availability. To ensure the field is available for 6 more releases, it is removed in the 14.0 major release (and not 13.0). ![]() Removed in GitLab 14.0: Field deprecated in Reason 12.7 GitLab traditionally has 12 minor releases per major release. The following fields are deprecated in different minor releases, but both The deprecation message provides an alternative for the deprecated schema item, If you use the GraphQL API, we recommend you remove the deprecated schema from your GraphQLĪPI calls as soon as possible to avoid experiencing breaking changes. To avoid having a breaking change affect your integrations, you shouldįamiliarize yourself with the deprecation and removal process. When creating a breaking change, GitLab follows a deprecation and removal process.įields behind a feature flag and disabled by default do not follow the deprecation and removal process, and can be removed at any time without notice. These changes are considered breaking changes, andĬan include removing or renaming fields, arguments, or other parts of the schema. However, GitLab sometimes changes the GraphQL API in a way that is not backward-compatible. The GitLab GraphQL API is versionless and changes to the API are primarily backward-compatible. The get started page includes different methods to customize GraphQL queries. You can work with sample queries that pull data from public projects on : Or on your self-managed GitLab instance on GraphiQLĮxplore the GraphQL API using the interactive GraphiQL explorer, The GitLab GraphQL API endpoint is located at /api/graphql. The reference is automatically generated from the GitLab GraphQL schema and You can view the available resources in the GraphQL API reference. If you’re new to the GitLab GraphQL API, see Get started with GitLab GraphQL API. Supporting two APIs in parallel, they should share implementations as much as There are no plans to deprecate the REST API. To help us meet this vision, the frontend should use GraphQL in preference to Possible in the REST API should also be possible in the GraphQL API. To achieve this, it needs full coverage - anything We want the GraphQL API to be the primary means of interacting This enables us to have a versionless API. To the API without creating breaking changes. There are no fixed endpoints and no data model, so you can add ![]() To consume the API and avoid manual parsing. GraphQL data is arranged in types, so your client can use Request the exact data you need, and therefore limit the number of requests you need. Enabled and made generally available in GitLab 12.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |