Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

graphql.rb

  • Luke Duncalfe's avatar
    ccb4edbc
    Improve GraphQL Authorization DSL · ccb4edbc
    Luke Duncalfe authored
    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
    ccb4edbc
    History
    Improve GraphQL Authorization DSL
    Luke Duncalfe authored
    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