gitlab-org--gitlab-foss/app/finders
Douwe Maan c620c40575 Merge branch 'issue_18135' into 'master'
Todos sorting dropdown

Implements #18135 

![todos_sorting](/uploads/bff76827c421628134dfb8b864e47c74/todos_sorting.png)  


- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- Tests
  - [x] Added for this feature/bug
  - [x] All builds are passing
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

See merge request !5691
2016-08-19 23:06:30 +00:00
..
README.md
branches_finder.rb
contributed_projects_finder.rb
group_projects_finder.rb
groups_finder.rb
issuable_finder.rb
issues_finder.rb
joined_groups_finder.rb
merge_requests_finder.rb
milestones_finder.rb
move_to_project_finder.rb
notes_finder.rb
personal_projects_finder.rb
pipelines_finder.rb
projects_finder.rb
snippets_finder.rb
todos_finder.rb Merge branch 'issue_18135' into 'master' 2016-08-19 23:06:30 +00:00
trending_projects_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.