summaryrefslogtreecommitdiff
path: root/config/initializers
diff options
context:
space:
mode:
authorLuke Duncalfe <lduncalfe@eml.cc>2019-02-18 14:19:49 +1300
committerLuke Duncalfe <lduncalfe@eml.cc>2019-02-26 10:22:12 +1300
commitccb4edbca1aa7e94a76a5a8d361af02fd093e1b9 (patch)
tree833f8cd26fc162cc3b71e0a46ed4db69d4e69cde /config/initializers
parent7ff0c8ae57e6a88c86afae4f8e08bfacfb34d761 (diff)
downloadgitlab-ce-ccb4edbca1aa7e94a76a5a8d361af02fd093e1b9.tar.gz
Improve GraphQL Authorization DSL
Previously GraphQL field authorization happened like this: class ProjectType field :my_field, MyFieldType do authorize :permission end end This change allowed us to authorize like this instead: class ProjectType field :my_field, MyFieldType, authorize: :permission end A new initializer registers the `authorize` metadata keyword on GraphQL Schema Objects and Fields, and we can collect this data within the context of Instrumentation like this: field.metadata[:authorize] The previous functionality of authorize is still being used for mutations, as the #authorize method here is called at during the code that executes during the mutation, rather than when a field resolves. https://gitlab.com/gitlab-org/gitlab-ce/issues/57828
Diffstat (limited to 'config/initializers')
-rw-r--r--config/initializers/graphql.rb4
1 files changed, 4 insertions, 0 deletions
diff --git a/config/initializers/graphql.rb b/config/initializers/graphql.rb
new file mode 100644
index 00000000000..1ed93019329
--- /dev/null
+++ b/config/initializers/graphql.rb
@@ -0,0 +1,4 @@
+# frozen_string_literal: true
+
+GraphQL::Field.accepts_definitions(authorize: GraphQL::Define.assign_metadata_key(:authorize))
+Types::BaseField.accepts_definition(:authorize)