summaryrefslogtreecommitdiff
path: root/spec/graphql/resolvers
Commit message (Collapse)AuthorAgeFilesLines
* Remove code related to object hierarchy in MySQLremove-nested-groups-checksHeinrich Lee Yu2019-07-251-1/+1
| | | | | These are not required because MySQL is not supported anymore
* Use :complexity_multiplier only with connectionsBrett Walker2019-06-053-12/+14
| | | | This helps reduce complexity for non-connections
* Add Namespace and ProjectStatistics to GraphQL APIAlessio Caiazza2019-06-031-0/+69
| | | | | | We can query namespaces, and nested projects. Projects now exposes statistics
* Merge branch 'graphql-tree' into 'master'Nick Thomas2019-05-221-0/+35
|\ | | | | | | | | Added repository files to GraphQL API See merge request gitlab-org/gitlab-ce!28325
| * Added repository files to GraphQL APIPhil Hughes2019-05-221-0/+35
| |
* | Use BatchModelLoader for parent in GroupType62066-use-batchmodelloader-for-grouptypeBrett Walker2019-05-201-0/+32
|/
* GraphQL - Add extra complexity for resolversJan Provaznik2019-05-064-0/+38
| | | | | | | | | | | | | | | | | | If a field is a resolver, its complexity is automatically increased. By default we add extra points for sort and search arguments (which will be common for various resolvers). For specific resolvers we add field-specific complexity, e.g. for Issues complexity is increased if we filter issues by `labelName` (because then SQL query is more complex). We may want to tune these values in future depending on real-life results. Complexity is also dependent on the number of loaded nodes, but only if we don't search by specific ID(s). Also added complexity is limited (by default only twice more than child complexity) - the reason is that although it's more complex to process more items, the complexity increase is not linear (there is not so much difference between loading 10, 20 or 100 records from DB).
* Port changes for design management to CEBob Van Landuyt2019-04-291-70/+85
| | | | | | This ports the changes from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10462/ to CE
* Add metadata about the GitLab server to GraphQLNick Thomas2019-03-051-0/+11
|
* Add GraphQL filters for issuables (state, labels, time fields)Rémy Coutable2019-02-211-11/+58
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Implement singular iid for IssuesResolver and ProjectTypeLin Jen-Shin2019-02-141-0/+4
|
* Add tests for BaseResolver and update accordinglyLin Jen-Shin2019-02-142-9/+54
|
* Add field mergeRequests for project in GraphQLLin Jen-Shin2019-02-141-4/+6
| | | | And fix the tests so that it won't run into circular paths.
* Add argument iids to IssuesResolverLin Jen-Shin2019-02-011-0/+20
|
* Enable the Layout/ExtraSpacing cop56392-enable-the-layout-extraspacing-copRémy Coutable2019-01-241-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Suggests issues when typing titlePhil Hughes2018-11-271-0/+40
| | | | | | | | | | | | | | | This suggests possibly related issues when the user types a title. This uses GraphQL to allow the frontend to request the exact data that is requires. We also get free caching through the Vue Apollo plugin. With this we can include the ability to import .graphql files in JS and Vue files. Also we now have the Vue test utils library to make testing Vue components easier. Closes #22071
* Add pipeline lists to GraphQLBob Van Landuyt2018-07-043-0/+104
| | | | | | | | | 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.
* Allow querying a single MR within a projectBob Van Landuyt2018-06-151-18/+5
| | | | | | | | 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.
* Initial setup GraphQL using graphql-ruby 1.8Bob Van Landuyt2018-06-062-0/+90
- 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