- 06 3月, 2019 1 次提交
-
-
由 Bob Van Landuyt 提交于
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.
-
- 05 3月, 2019 1 次提交
-
-
由 Nick Thomas 提交于
-
- 14 2月, 2019 1 次提交
-
-
由 Lin Jen-Shin 提交于
And fix the tests so that it won't run into circular paths.
-
- 24 1月, 2019 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 21 12月, 2018 1 次提交
-
-
由 Jasper Maes 提交于
-
- 26 7月, 2018 1 次提交
-
-
由 Bob Van Landuyt 提交于
This is mainly the setup of mutations for GraphQL. Including authorization and basic return type-structure.
-
- 04 7月, 2018 1 次提交
-
-
由 Bob Van Landuyt 提交于
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.
-
- 15 6月, 2018 1 次提交
-
-
由 Bob Van Landuyt 提交于
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.
-
- 06 6月, 2018 4 次提交
-
-
由 Bob Van Landuyt 提交于
- 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
-
由 Bob Van Landuyt 提交于
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 提交于
-
由 Nick Thomas 提交于
-