summaryrefslogtreecommitdiff
path: root/app/controllers/graphql_controller.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42GitLab Bot2021-02-181-0/+5
|
* Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42GitLab Bot2020-12-171-1/+5
|
* Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42GitLab Bot2020-10-211-2/+14
|
* Add latest changes from gitlab-org/gitlab@13-4-stable-eeGitLab Bot2020-09-191-1/+9
|
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-201-1/+13
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-021-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-181-0/+1
|
* Propagate argument errors as execution errorsajk-handle-gql-errorsAlex Kalderimis2019-07-301-0/+4
|
* Remove `:graphql` feature flagcharlie ablett2019-07-091-5/+0
| | | | | | | | - 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`
* Enable GraphQL batch requestsPhil Hughes2019-05-291-1/+2
|
* Enables GraphQL batch requestsPhil Hughes2019-05-281-7/+39
| | | | | | | | | 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.
* Add API access check to GraphqlFelipe Artur2019-03-271-0/+5
| | | | Check if user can access API on GraphqlController
* Allow GraphQL requests without CSRF tokenBob Van Landuyt2019-03-061-1/+8
| | | | | | | | | | | | With this we allow authentication using a session or using personal access token. Authentication using a session, and CSRF token makes it easy to play with GraphQL from the Graphiql endpoint we expose. But we cannot enforce CSRF validity, otherwise authentication for regular API clients would fail when they use personal access tokens to authenticate.
* Enable GraphQL API endpointPhil Hughes2018-12-131-1/+1
|
* Remove issue_suggestions feature flagPhil Hughes2018-12-131-1/+1
| | | | Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55166
* Merge branch 'security-fix-pat-web-access' into 'master'Cindy Pallares2018-11-281-0/+1
| | | | | [master] Resolve "Personal access token with only `read_user` scope can be used to authenticate any web request" See merge request gitlab/gitlabhq!2583
* Enable frozen string in app/controllers/**/*.rbrepo-forks/gitlab-ce-frozen-string-app-controllergfyoung2018-09-181-0/+2
| | | | | | | | | | | | Enables frozen string for the following: * app/controllers/*.rb * app/controllers/admin/**/*.rb * app/controllers/boards/**/*.rb * app/controllers/ci/**/*.rb * app/controllers/concerns/**/*.rb Partially addresses #47424.
* Handle exceptions outside the GraphQL schemaBob Van Landuyt2018-06-051-21/+17
| | | | | This allows us to report JSON parse exceptions to clients and ignore them in sentry.
* Add a minimal GraphQL APINick Thomas2018-06-051-0/+49