5ee7884d91
If a field is a resolver, its complexity is automatically increased. By default we add extra points for sort and search arguments (which will be common for various resolvers). For specific resolvers we add field-specific complexity, e.g. for Issues complexity is increased if we filter issues by `labelName` (because then SQL query is more complex). We may want to tune these values in future depending on real-life results. Complexity is also dependent on the number of loaded nodes, but only if we don't search by specific ID(s). Also added complexity is limited (by default only twice more than child complexity) - the reason is that although it's more complex to process more items, the complexity increase is not linear (there is not so much difference between loading 10, 20 or 100 records from DB).
35 lines
955 B
Ruby
35 lines
955 B
Ruby
# frozen_string_literal: true
|
|
|
|
module ResolvesPipelines
|
|
extend ActiveSupport::Concern
|
|
|
|
included do
|
|
type [Types::Ci::PipelineType], null: false
|
|
argument :status,
|
|
Types::Ci::PipelineStatusEnum,
|
|
required: false,
|
|
description: "Filter pipelines by their status"
|
|
argument :ref,
|
|
GraphQL::STRING_TYPE,
|
|
required: false,
|
|
description: "Filter pipelines by the ref they are run for"
|
|
argument :sha,
|
|
GraphQL::STRING_TYPE,
|
|
required: false,
|
|
description: "Filter pipelines by the sha of the commit they are run for"
|
|
end
|
|
|
|
class_methods do
|
|
def resolver_complexity(args)
|
|
complexity = super
|
|
complexity += 2 if args[:sha]
|
|
complexity += 2 if args[:ref]
|
|
|
|
complexity
|
|
end
|
|
end
|
|
|
|
def resolve_pipelines(project, params = {})
|
|
PipelinesFinder.new(project, context[:current_user], params).execute
|
|
end
|
|
end
|