- Mar 16, 2020
-
-
GitLab Bot authored
-
- Mar 14, 2020
-
-
GitLab Bot authored
-
- Mar 12, 2020
-
-
GitLab Bot authored
-
- Mar 02, 2020
-
-
GitLab Bot authored
-
- Feb 27, 2020
-
-
GitLab Bot authored
-
- Feb 26, 2020
-
-
GitLab Bot authored
-
- Feb 24, 2020
-
-
GitLab Bot authored
-
- Feb 05, 2020
-
-
GitLab Bot authored
-
- Jan 31, 2020
-
-
GitLab Bot authored
-
- Jan 29, 2020
-
-
GitLab Bot authored
-
- Jan 25, 2020
-
-
GitLab Bot authored
-
- Jan 23, 2020
-
-
GitLab Bot authored
-
- Jan 16, 2020
-
-
GitLab Bot authored
-
- Jan 07, 2020
-
-
GitLab Bot authored
-
- Dec 23, 2019
-
-
GitLab Bot authored
-
- Dec 16, 2019
-
-
GitLab Bot authored
-
- Dec 13, 2019
-
-
GitLab Bot authored
-
- Dec 10, 2019
-
-
GitLab Bot authored
-
- Dec 06, 2019
-
-
GitLab Bot authored
-
- Nov 27, 2019
-
-
GitLab Bot authored
-
- Nov 19, 2019
-
-
GitLab Bot authored
-
- Nov 14, 2019
-
-
GitLab Bot authored
-
- Oct 17, 2019
-
-
GitLab Bot authored
-
- Oct 04, 2019
-
-
GitLab Bot authored
-
- Oct 03, 2019
-
-
GitLab Bot authored
-
- Sep 18, 2019
-
-
GitLab Bot authored
-
- Sep 16, 2019
-
-
GitLab Bot authored
-
- Sep 13, 2019
-
-
GitLab Bot authored
-
- 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
-
- Aug 26, 2019
-
-
The `GraphQL::Function` has been deprecated in favor of resolvers.
-
- Jun 03, 2019
-
-
Bob Van Landuyt authored
Since the `GraphQL::ID_TYPE` usages should represent globally unique ids, this changes some fields for which this is not the case into strings. The `ID_TYPE` is a specialised, so this change should be backwards compatible. https://graphql-ruby.org/type_definitions/scalars.html
-
Alessio Caiazza authored
We can query namespaces, and nested projects. Projects now exposes statistics
-
- May 31, 2019
-
-
Brett Walker authored
and allow passing of child_complexity to the 'resolver_complexity' metho
-
- May 22, 2019
-
-
Phil Hughes authored
-
- May 20, 2019
-
-
Yoginth authored
-
- May 06, 2019
-
-
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).
-
- 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 23, 2019
-
-
Brett Walker authored
Add new query for Groups, with new GroupType and NamespaceType
-
- Mar 05, 2019
-
-
Nick Thomas authored
-
- Feb 21, 2019
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-