Update previously unassigned topics.

This line was added in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53176
but was meant to be removed before the change was merged
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53176#note_514749869.

We do not use it, it can be replaced by introspection queries, and
it complicates development.

The `gitlab:graphql:schema:dump` rake task now generates the file
in the `./tmp` directory.

The documentation is updated to mention the impact on front-end
development.

Dan Jensen authored 4 years ago and Tim Zallmann committed 4 years ago

The documentation refers to "breaking changes" in multiple places,
but did not define the term. This introduces a definition in the
contribution guide, and adds links to this definition in multiple
places.

Luke Duncalfe authored 4 years ago and Evan Read committed 4 years ago

Adds client and developer documentation for the GraphQL API's limits:

- Complexity
- Max page size
- Request timeout

This broken anchor link was introduced yesterday, somewhere else.
Fixing so 'master' remains unbroken.

The previous URL had two drawbacks:

1. It didn't match what the title was about (`Assignments to DevOps
   Stages and Groups`, and the anchor was `#designated-technical-writers`).
2. It didn't account for the other sections, like development and API
   guidelines.

- add links and template

Add additional none/unassigned metadata to docs

- Use GroupMembersFinder
- No bulk loading yet

Max Woolf authored 4 years ago and Oswaldo Ferreir committed 4 years ago

Users can now query the GraphQL API
to pull out an entire list of users,
or filter by a subset of IDs or
usernames

These words should not be treated as spelling errors by Vale's
spelling checker.

Adds a root user query to search
for a user by username or id

Some changes from "info" to "information" couldn't be made if
"info" appears in the UI.

Some instances of "info" remain in the GraphQL reference.

Evan Read authored 4 years ago and Marcel Amirault committed 4 years ago

Mostly in Geo and HA documentation.

Marcel Amirault authored 5 years ago and Achilleas Pipinellis committed 5 years ago

The URLs needs hyphens now, so did a find and
replace to add them.

Added resolvers for project and user snippets.

Charlie Ablett authored 5 years ago and Evan Read committed 5 years ago

- Query examples with GitLab context
- Queries, mutations, data types
- Arguments and input types
- links to documentation
- Sorting, pagination, slicing
- Overview is a hands-on tutorial with live examples
- Index page has links to both with an extra Getting Started section
- Add create, update, delete mutation examples
- Add command line example

Use the [built-in Rake Task available as part of the graphql-ruby
gem](https://github.com/rmosolgo/graphql-ruby/blob/master/lib/graphql/rake_task.rb)
in order to generate both
[IDL](https://www.prisma.io/blog/graphql-sdl-schema-definition-language-6755bcb9ce51)
and JSON schema files.

Also adds a rake task that checks to make sure the files are up-to-date
as well as runs the rake task in our CI

Marcel Amirault authored 5 years ago and Achilleas Pipinellis committed 5 years ago

Update links in various admin, api and raketasks docs

Yorick Peterse authored 5 years ago and Achilleas Pipinellis committed 5 years ago

This changes any mention of gitlab-ce to gitlab-foss, and any mention of
gitlab-ee to just gitlab.

Adds more friendly docs for GraphQl implementation

- Remove `FeatureConstrainer` call wrapping api endpoint
- Remove `Feature.enabled?(:graphql)` conditionals in back and frontend
- Modify graphql test to be graphql flag agnostic
- Remove api routing spec
- Remove frontend feature flag via `gon`

Marcel Amirault authored 5 years ago and Achilleas Pipinellis committed 5 years ago

Previously, we used brackets to denote the tier badges,
but this made Kramdown, the docs site Markdown renderer,
show many warnings when building the site. This is now
fixed by using parentheses instead of square brackets.

This was caused by [PREMIUM] looking like a link to
Kramdown, which couldn't find a URL there.

See:
- https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484
- https://gitlab.com/gitlab-org/gitlab-ce/issues/63800

We can query namespaces, and nested projects.

Projects now exposes statistics

Enabling GraphQL batch requests allows for multiple queries
to be sent in 1 request reducing the amount of requests
we send to the server.

Responses come come back in the same order as the queries were
provided.