gitlab-org--gitlab-foss/app/finders
Yorick Peterse d6a8021ea1 Scope issue projects to a Group when possible
When using IssuableFinder with a Group we can greatly reduce the amount
of projects operated on (due to not including all public/internal
projects) by simply passing it down to the ProjectsFinder class.

This reduces the timings of the involved queries from roughly 300
ms to roughly 20 ms.

Fixes gitlab-org/gitlab-ce#4071, gitlab-org/gitlab-ce#3707
2016-01-18 12:27:33 +01:00
..
contributed_projects_finder.rb Refactor ProjectsFinder to not pluck IDs 2015-11-18 13:05:45 +01:00
issuable_finder.rb Scope issue projects to a Group when possible 2016-01-18 12:27:33 +01:00
issues_finder.rb
merge_requests_finder.rb
milestones_finder.rb sort milestones by due_date 2015-12-03 08:53:34 -06:00
notes_finder.rb css improvements 2015-11-19 01:25:59 +02:00
personal_projects_finder.rb Return internal projects in PersonalProjectsFinder 2015-11-18 15:08:28 +01:00
projects_finder.rb Port GitLab EE ProjectsFinder changes 2015-11-20 15:53:04 +01:00
README.md Set milestone on new issue when creating issue from index with milestone filter active. 2015-05-27 14:22:11 +02:00
snippets_finder.rb
trending_projects_finder.rb Revamp trending projects query 2015-10-06 17:26:32 +02:00

Finders

This type of classes responsible for collection items based on different conditions. To prevent lookup methods in models like this:

class Project
  def issues_for_user_filtered_by(user, filter)
    # A lot of logic not related to project model itself
  end
end

issues = project.issues_for_user_filtered_by(user, params)

Better use this:

issues = IssuesFinder.new(project, user, filter).execute

It will help keep models thiner.