gitlab-org--gitlab-foss/app/finders
Dmitriy Zaporozhets 26f28f9654 Show members of parent groups on project members page
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2017-03-09 10:23:57 +02:00
..
README.md
access_requests_finder.rb
branches_finder.rb
contributed_projects_finder.rb
environments_finder.rb
group_members_finder.rb Show members of parent groups on project members page 2017-03-09 10:23:57 +02:00
group_projects_finder.rb
groups_finder.rb
issuable_finder.rb Improve issues filtering performance 2017-03-06 14:45:50 +01:00
issues_finder.rb Improve issues filtering performance 2017-03-06 14:45:50 +01:00
joined_groups_finder.rb
labels_finder.rb
members_finder.rb Show members of parent groups on project members page 2017-03-09 10:23:57 +02:00
merge_requests_finder.rb Improve issues filtering performance 2017-03-06 14:45:50 +01:00
milestones_finder.rb
move_to_project_finder.rb
notes_finder.rb
personal_access_tokens_finder.rb apply codestyle and implementation changes to the respective feature code 2017-03-06 19:18:26 +00:00
personal_projects_finder.rb
pipelines_finder.rb
projects_finder.rb
snippets_finder.rb
tags_finder.rb
todos_finder.rb
union_finder.rb

README.md

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.