- Sep 04, 2019
-
-
- Due to https://github.com/exAspArk/batch-loader/pull/32, we changed BatchLoader.for into BatchLoader::GraphQL.for - since our results are wrapped in a BatchLoader::GraphQL, calling `sync` during authorization is required to get real object - `graphql` now has it's own authorization system. Our `authorized?` method conflicted and required renaming
-
- Jul 30, 2019
-
-
Alex Kalderimis authored
This improves the graphql test helpers, failing earlier and more explicitly.
-
- Jul 25, 2019
-
-
Thong Kuah authored
Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
-
- Jul 10, 2019
-
- Jun 28, 2019
-
-
Luke Duncalfe authored
Adding new `AddAwardEmoji`, `RemoveAwardEmoji` and `ToggleAwardEmoji` GraphQL mutations. Adding new `#authorized_find_with_pre_checks!` and (unused, but for completeness `#authorized_find_with_post_checks!`) authorization methods. These allow us to perform an authorized find, and run our own additional checks before or after the authorization runs. https://gitlab.com/gitlab-org/gitlab-ce/issues/62826
-
- Jun 15, 2019
-
-
Patrick Derichs authored
Add specs for task completion status (graphql) Fix style issues Changed format of constants in spec Refactor specs to reduce creation of records Reduce parameters to merge request creation Use set's for project and user Move let's out of it_behaves_like block Fix description parameter Fix format of lets Use dig to get task completion status out of graphql response Modified rspec output Add changelog entry
-
- May 28, 2019
-
-
Phil Hughes authored
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.
-
- May 10, 2019
-
-
Bob Van Landuyt authored
Avoid counting on Rails eager loading the GraphQL types, but preload them before the specs. This would avoid loading the schema in 2 separate threads concurrently (1 inside the specs, 1 inside the test-server that will receive requests). Loading the schema in parallel like that could cause duplicate definition errors.
-
- May 06, 2019
-
-
Ken Ding authored
58404 - add change log 58404 - add spec 58404 - add more spec to test depth 2 58404 - fix spec 58404 - fix rubocop 58404 - refactor the code by Bob's advice 58404 - revert changes of all_graphql_fields_for 58404 - change text only 58404 - fix rspec according to gitlab's standard 58404 - revert previous spec 58404 - fix rubocop
-
- Apr 29, 2019
-
-
Bob Van Landuyt authored
This ports the changes from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10462/ to CE
-
- Apr 11, 2019
-
-
Brett Walker authored
-
- Apr 04, 2019
-
-
Brett Walker authored
It makes all Types::BaseField default to a complexity of 1. Queries themselves now have limited complexity, scaled to the type of user: no user, authenticated user, or an admin user.
-
- Mar 13, 2019
-
-
Nick Thomas authored
-
- Mar 06, 2019
-
-
Bob Van Landuyt authored
These adjustments make sure our GraphQL helpers support rendering queries for empty fields like this: { echo(text: "Hello world") } Instead of like this: { echo(text: "Hello world") { } } The latter would be an invalid query, causing parsing errors.
-
- Mar 05, 2019
-
-
Nick Thomas authored
-
- Feb 14, 2019
-
-
Lin Jen-Shin authored
And fix the tests so that it won't run into circular paths.
-
- Jan 24, 2019
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- Dec 21, 2018
-
-
Jasper Maes authored
-
- Jul 25, 2018
-
-
Bob Van Landuyt authored
This is mainly the setup of mutations for GraphQL. Including authorization and basic return type-structure.
-
- Jul 04, 2018
-
-
Bob Van Landuyt authored
This adds Keyset pagination to GraphQL lists. PoC for that is pipelines on merge requests and projects. When paginating a list, the base-64 encoded id of the ordering field (in most cases the primary key) can be passed in the `before` or `after` GraphQL argument.
-
- Jun 15, 2018
-
-
Bob Van Landuyt authored
This allows the user to get a single MR nested in a GraphQL project query. Since we need the full path and the iid anyway, this makes more sense than having a root query that needs the full path as well.
-
- Jun 06, 2018
-
-
Bob Van Landuyt authored
- All definitions have been replaced by classes: http://graphql-ruby.org/schema/class_based_api.html - Authorization & Presentation have been refactored to work in the class based system - Loaders have been replaced by resolvers - Times are now coersed as ISO 8601
-
- Jun 05, 2018
-
-
Bob Van Landuyt authored
By specifying a presenter for the object type, we can keep the logic out of `GitlabSchema`. The presenter gets initialized using the object being presented, and the context (including the `current_user`).
-
Nick Thomas authored
-
Nick Thomas authored
-