Skip to content
Snippets Groups Projects
Select Git revision
  • move-gl-dropdown
  • improve-table-pagination-spec
  • move-markdown-preview
  • winh-fix-merge-request-spec
  • master default
  • index-namespaces-lower-name
  • winh-single-karma-test
  • 10-3-stable
  • 36782-replace-team-user-role-with-add_role-user-in-specs
  • winh-modal-internal-state
  • tz-ide-file-icons
  • 38869-milestone-select
  • update-autodevops-template
  • jivl-activate-repo-cookie-preferences
  • qa-add-deploy-key
  • docs-move-article-ldap
  • 40780-choose-file
  • 22643-manual-job-page
  • refactor-cluster-show-page-conservative
  • dm-sidekiq-versioning
  • v10.4.0.pre
  • v10.3.0
  • v10.3.0-rc5
  • v10.3.0-rc4
  • v10.3.0-rc3
  • v10.3.0-rc2
  • v10.2.5
  • v10.3.0-rc1
  • v10.0.7
  • v10.1.5
  • v10.2.4
  • v10.2.3
  • v10.2.2
  • v10.2.1
  • v10.3.0.pre
  • v10.2.0
  • v10.2.0-rc4
  • v10.2.0-rc3
  • v10.1.4
  • v10.2.0-rc2
40 results

project_snippet.rb

Forked from GitLab.org / GitLab FOSS
Source project has a limited visibility.
  • Yorick Peterse's avatar
    580d2501
    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.
    Refactor Participable
    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.