BigW Consortium Gitlab

  1. 05 Jul, 2016 3 commits
  2. 30 Jun, 2016 1 commit
  3. 29 Jun, 2016 1 commit
  4. 23 Jun, 2016 1 commit
  5. 16 Jun, 2016 2 commits
  6. 15 Jun, 2016 3 commits
  7. 14 Jun, 2016 4 commits
  8. 13 Jun, 2016 1 commit
  9. 10 Jun, 2016 1 commit
  10. 03 Jun, 2016 2 commits
  11. 01 Jun, 2016 1 commit
    • Refactor Participable · 580d2501
      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.
  12. 30 May, 2016 1 commit
  13. 22 May, 2016 1 commit
  14. 14 May, 2016 3 commits
  15. 13 May, 2016 1 commit
  16. 12 May, 2016 1 commit
  17. 09 May, 2016 1 commit
  18. 29 Apr, 2016 1 commit
  19. 20 Apr, 2016 1 commit
  20. 18 Apr, 2016 10 commits