ccb4edbca1
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 |
||
---|---|---|
.. | ||
access_matchers.rb | ||
access_matchers_for_controller.rb | ||
background_migrations_matchers.rb | ||
be_a_binary_string.rb | ||
be_like_time.rb | ||
be_url.rb | ||
be_utf8.rb | ||
be_valid_commit.rb | ||
disallow_request_matchers.rb | ||
exceed_query_limit.rb | ||
execute_check.rb | ||
gitaly_matchers.rb | ||
gitlab_git_matchers.rb | ||
graphql_matchers.rb | ||
have_emoji.rb | ||
have_gitlab_http_status.rb | ||
have_issuable_counts.rb | ||
include_module.rb | ||
issuable_matchers.rb | ||
markdown_matchers.rb | ||
match_file.rb | ||
match_ids.rb | ||
metric_counter_matcher.rb | ||
navigation_matcher.rb | ||
pagination_matcher.rb | ||
query_matcher.rb | ||
satisfy_matchers.rb | ||
security_header_matcher.rb | ||
user_status_matcher.rb |