gitlab-org--gitlab-foss/lib/banzai/commit_renderer.rb

module Banzai
  module CommitRenderer
    ATTRIBUTES = [:description, :title].freeze

    def self.render(commits, project, user = nil)
      obj_renderer = ObjectRenderer.new(user: user, default_project: project)

      ATTRIBUTES.each { |attr| obj_renderer.render(commits, attr) }
    end
  end
end
Adds cacheless render to Banzai object render 2017-08-23 12:53:29 -04:00			`module Banzai`
			`module CommitRenderer`
			`ATTRIBUTES = [:description, :title].freeze`

			`def self.render(commits, project, user = nil)`
Support Markdown rendering using multiple projects This refactors the Markdown pipeline so it supports the rendering of multiple documents that may belong to different projects. An example of where this happens is when displaying the event feed of a group. In this case we retrieve events for all projects in the group. Previously we would group events per project and render these chunks separately, but this would result in many SQL queries being executed. By extending the Markdown pipeline to support this out of the box we can drastically reduce the number of SQL queries. To achieve this we introduce a new object to the pipeline: Banzai::RenderContext. This object simply wraps two other objects: an optional Project instance, and an optional User instance. On its own this wouldn't be very helpful, but a RenderContext can also be used to associate HTML documents with specific Project instances. This work is done in Banzai::ObjectRenderer and allows us to reuse as many queries (and results) as possible. 2018-04-03 09:45:17 -04:00			`obj_renderer = ObjectRenderer.new(user: user, default_project: project)`
Adds cacheless render to Banzai object render 2017-08-23 12:53:29 -04:00
			`ATTRIBUTES.each { \|attr\| obj_renderer.render(commits, attr) }`
			`end`
			`end`
			`end`