gitlab-org--gitlab-foss/config/initializers/graphql.rb

# frozen_string_literal: true

GraphQL::Field.accepts_definitions(authorize: GraphQL::Define.assign_metadata_key(:authorize))
GraphQL::Schema::Field.accepts_definition(:authorize)
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 2019-02-17 20:19:49 -05:00			`# frozen_string_literal: true`

			`GraphQL::Field.accepts_definitions(authorize: GraphQL::Define.assign_metadata_key(:authorize))`
Types::BaseField accepts authorize after reload When working on files in `app/graphql` the code correctly gets autoloaded. However, the redefined `Types::BaseField` would never receive the `.accepts_definition` call, causing all queries after a reload to fail. Calling `.accepts_definition` on its superclass makes sure the reloaded version also has the `authorize` definition specified. 2019-03-01 12:30:42 -05:00			`GraphQL::Schema::Field.accepts_definition(:authorize)`