- 14 Aug, 2017 1 commit
-
-
Robert Speicher authored
An upcoming update to rubocop-gitlab-security added additional violations.
-
- 25 Jan, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 18 Jan, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 15 Jul, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 21 Jun, 2016 1 commit
-
-
Paco Guzman authored
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 01 Jun, 2016 1 commit
-
-
Yorick Peterse authored
There are several changes to this module: 1. The use of an explicit stack in Participable#participants 2. Proc behaviour has been changed 3. Batch permissions checking == Explicit Stack Participable#participants no longer uses recursion to process "self" and all child objects, instead it uses an Array and processes objects in breadth-first order. This allows us to for example create a single Gitlab::ReferenceExtractor instance and pass this to any Procs. Re-using a ReferenceExtractor removes the need for running potentially many SQL queries every time a Proc is called on a new object. == Proc Behaviour Changed Previously a Proc in Participable was expected to return an Array of User instances. This has been changed and instead it's now expected that a Proc modifies the Gitlab::ReferenceExtractor passed to it. The return value of the Proc is ignored. == Permissions Checking The method Participable#participants uses Ability.users_that_can_read_project to check if the returned users have access to the project of "self" _without_ running multiple SQL queries for every user.
-
- 21 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 15 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 15 Oct, 2015 1 commit
-
-
Douwe Maan authored
-
- 14 Oct, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 12 Oct, 2015 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 24 Jun, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
* store @participants in variable * store result of subscribed? call into variable In total it reduce amount of SQL queries for issue with 10 comments/participants twice. Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 15 May, 2015 1 commit
-
-
Douwe Maan authored
-
- 14 May, 2015 1 commit
-
-
Douwe Maan authored
-
- 24 Apr, 2015 4 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-