1. 30 Jun, 2016 1 commit
  2. 29 Jun, 2016 1 commit
    • Stan Hu's avatar
      Memoize the maximum access level for the author of notes · 5ef022c499e5
      Stan Hu authored
      In #19273, we saw that retrieving ProjectTeam#human_max_access for each
      note takes the bulk of the time when rendering certain issues or merge requests.
      We observe that most of the comments in an issue are typically done by the
      same users. This MR memoizes the max access level by user ID.
      5ef022c499e5
  3. 28 Jun, 2016 2 commits
  4. 27 Jun, 2016 4 commits
  5. 24 Jun, 2016 1 commit
    • Yorick Peterse's avatar
      Support for rendering/redacting multiple documents · 8c4e1063826d
      Yorick Peterse authored
      This commit changes the way certain documents are rendered (currently
      only Notes) and how documents are redacted. Previously both rendering
      and redacting would run on a per document basis. The result of this was
      that for every document we'd have to run countless queries just to
      figure out if we could display a set of links or not.
      
      This commit changes things around so that redacting Markdown documents
      is no longer tied into the html-pipeline Gem. This in turn allows it to
      redact multiple documents in a single pass, thus reducing the number of
      queries needed.
      
      In turn rendering issue/merge request notes has been adjusted to take
      advantage of this new setup. Instead of rendering Markdown somewhere
      deep down in a view the Markdown is rendered and redacted in the
      controller (taking the current user and all that into account). This has
      been done in such a way that the "markdown()" helper method can still be
      used on its own.
      
      This particular commit also paves the way for caching rendered HTML on
      object level. Right now there's an accessor method Note#note_html which
      is used for setting/getting the rendered HTML. Once we cache HTML on row
      level we can simply change this field to be a column and call a "save"
      whenever needed and we're pretty much done.
      8c4e1063826d
  6. 23 Jun, 2016 6 commits
  7. 21 Jun, 2016 17 commits
  8. 20 Jun, 2016 8 commits